This is an automated email from the ASF dual-hosted git repository.
FreeAndNil pushed a change to branch Feature/312-more-hardening
in repository https://gitbox.apache.org/repos/asf/logging-log4net.git
discard 711e9b90 redact connection strings by keyword allowlist
discard 25439944 require PowerShell 7.4 in the release scripts
discard 4e0f52c2 remove graphify
discard 141cb8ef fix a signature verification bypass in the release scripts
add 6b6ffd73 fix a signature verification bypass in the release scripts
add 2a210ff3 remove graphify
add 8d8d1cf3 require PowerShell 7.4 in the release scripts
add ddf09c18 redact connection strings by keyword allowlist
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 (711e9b90)
\
N -- N -- N refs/heads/Feature/312-more-hardening (ddf09c18)
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:
...-string-allowlist.xml => 313-redact-connection-string-allowlist.xml} | 2 +-
.../{312-require-powershell-74.xml => 313-require-powershell-74.xml} | 2 +-
...erify-release-keys-bypass.xml => 313-verify-release-keys-bypass.xml} | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
rename src/changelog/3.4.1/{312-redact-connection-string-allowlist.xml =>
313-redact-connection-string-allowlist.xml} (89%)
rename src/changelog/3.4.1/{312-require-powershell-74.xml =>
313-require-powershell-74.xml} (91%)
rename src/changelog/3.4.1/{312-verify-release-keys-bypass.xml =>
313-verify-release-keys-bypass.xml} (91%)
