This is an automated email from the ASF dual-hosted git repository.
FreeAndNil pushed a change to branch Feature/314-background-sender
in repository https://gitbox.apache.org/repos/asf/logging-log4net.git
omit b5cdd547 wait for the background sender in the buffered mail test #314
omit cdbcb252 cite the right audit finding for the PowerShell version gate
#314
omit 3a62c28f cap the per-event retry in AdoNetAppender #314
omit f5efd752 send syslog datagrams through BackgroundSender #314
omit 0463e2ee do not open a second UDP socket in RemoteSyslogAppender #314
omit 41505ddd report a buffering appender that is still holding events #314
omit fd09d4a5 send mail from a background thread in the MailKit
SmtpAppender #314
omit be05efb8 bound a send in the MailKit SmtpAppender to 15 seconds #314
omit e94c0c33 bound a send in SmtpAppender to 15 seconds #314
omit be4415fc link Log4NetAssert into the test project #314
omit 193173a4 rename the unreleased 3.4.1 to 3.5.0 #314
omit fab3871d add a background sender for appenders that do network I/O #314
add 2e5cc831 verify in a GnuPG home of its own, not with --keyring #313
add 14ff8da3 add a background sender for appenders that do network I/O #314
add 47674226 rename the unreleased 3.4.1 to 3.5.0 #314
add fdfd9ab7 link Log4NetAssert into the test project #314
add 931b357b bound a send in SmtpAppender to 15 seconds #314
add 9e684208 bound a send in the MailKit SmtpAppender to 15 seconds #314
add 3cb96891 send mail from a background thread in the MailKit
SmtpAppender #314
add 0d034eaf report a buffering appender that is still holding events #314
add a6d3b807 do not open a second UDP socket in RemoteSyslogAppender #314
add f0d536fb send syslog datagrams through BackgroundSender #314
add 38567ea1 cap the per-event retry in AdoNetAppender #314
add be6211e7 cite the right audit finding for the PowerShell version gate
#314
add 1f4b8746 wait for the background sender in the buffered mail test #314
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (b5cdd547)
\
N -- N -- N refs/heads/Feature/314-background-sender (1f4b8746)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.github/workflows/build.yaml | 7 ++
scripts/verify-release.Tests.ps1 | 86 ++++++++++++++++++++++
scripts/verify-release.ps1 | 32 ++++----
scripts/verify-release.sh | 30 ++++----
.../3.5.0/313-verify-release-keys-bypass.xml | 5 +-
5 files changed, 127 insertions(+), 33 deletions(-)
create mode 100644 scripts/verify-release.Tests.ps1
