This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/com.h2database-h2-2.0.206
in repository https://gitbox.apache.org/repos/asf/commons-dbcp.git.
discard 4921a66 Bump h2 from 2.0.204 to 2.0.206
add a34eb6c Bump narayana-jta from 5.12.4.Final to 5.12.5.Final (#163)
add 552d06a Bump narayana-jta from 5.12.4.Final to 5.12.5.Final #163.
add 6902771 Bump spotbugs-maven-plugin from 4.5.2.0 to 4.5.3.0 (#161)
add def8541 Bump spotbugs-maven-plugin from 4.5.2.0 to 4.5.3.0 #161.
add 94029ce Bump h2 from 2.0.204 to 2.0.206
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 (4921a66)
\
N -- N -- N
refs/heads/dependabot/maven/com.h2database-h2-2.0.206 (94029ce)
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:
pom.xml | 4 ++--
src/changes/changes.xml | 6 ++++++
2 files changed, 8 insertions(+), 2 deletions(-)