This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/doxiaVersion-2.0.0-M11
in repository https://gitbox.apache.org/repos/asf/maven-doxia-converter.git
discard f47c182 Bump doxiaVersion from 2.0.0-M10-SNAPSHOT to 2.0.0-M11
add a29a4a3 Bump maven-gh-actions-shared to v4
add b0733a9 Bump doxiaVersion from 2.0.0-M10-SNAPSHOT to 2.0.0-M11
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 (f47c182)
\
N -- N -- N refs/heads/dependabot/maven/doxiaVersion-2.0.0-M11
(b0733a9)
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/maven-verify.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
