This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.codehaus.plexus-plexus-archiver-4.3.0
in repository https://gitbox.apache.org/repos/asf/axis-axis2-java-core.git
discard 06d77be045 Bump plexus-archiver from 4.2.7 to 4.3.0
add 97fbda935c comment back in tidy-maven-plugin with FIXME comment,
something is broke in systests/echo/pom.xml but I couldn't easily figure it out
add efc3cb52ba update 'Publish the site' section for git instead of svn in
release-process.md
add 4b188edb0b Add empty release note for 1.8.2
add 4b3f952666 Bump spring.version from 5.3.20 to 5.3.21
add 6844f5d1e4 Bump maven-common-artifact-filters from 3.2.0 to 3.3.0
add 908f8c6e53 Bump plexus-archiver from 4.2.7 to 4.3.0
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 (06d77be045)
\
N -- N -- N
refs/heads/dependabot/maven/org.codehaus.plexus-plexus-archiver-4.3.0
(908f8c6e53)
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:
modules/tool/axis2-repo-maven-plugin/pom.xml | 2 +-
pom.xml | 4 ++--
src/site/markdown/release-notes/1.8.2.md | 2 ++
src/site/markdown/release-process.md | 10 +++++-----
4 files changed, 10 insertions(+), 8 deletions(-)
create mode 100644 src/site/markdown/release-notes/1.8.2.md
