This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.hamcrest-hamcrest-core-3.0
in repository https://gitbox.apache.org/repos/asf/maven-doxia.git
discard b05e492c Bump org.hamcrest:hamcrest-core from 2.2 to 3.0
add 4fe6c91c [DOXIA-738] Add Footnote extention for Markdown module
add 0527ed3f use new Reproducible Central badge endpoint
add c35c571f [DOXIA-739] Disable source code highlighters for verbatim
blocks for Markdown
add d10c979d Bump org.apache.maven:maven-parent from 42 to 43
add 59d9d4d2 Bump org.hamcrest:hamcrest-core from 2.2 to 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 (b05e492c)
\
N -- N -- N
refs/heads/dependabot/maven/org.hamcrest-hamcrest-core-3.0 (59d9d4d2)
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:
README.md | 2 +-
.../java/org/apache/maven/doxia/parser/AbstractParserTest.java | 7 ++++++-
doxia-modules/doxia-module-markdown/pom.xml | 5 +++++
.../org/apache/maven/doxia/module/markdown/MarkdownParser.java | 3 +++
pom.xml | 2 +-
5 files changed, 16 insertions(+), 3 deletions(-)
