This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/v3/de.agilecoders.wicket.webjars-wicket-webjars-4.0.4
in repository https://gitbox.apache.org/repos/asf/causeway.git
omit 195f6bcdb6 Bump de.agilecoders.wicket.webjars:wicket-webjars from
4.0.3 to 4.0.4
add a795b89334 Bump wicket-bootstrap.version from 7.0.3 to 7.0.5
add a393187b40 Merge pull request #2473 from
apache/dependabot/maven/v3/wicket-bootstrap.version-7.0.5
add 64f05cd404 Bump de.agilecoders.wicket.webjars:wicket-webjars from
4.0.3 to 4.0.4
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 (195f6bcdb6)
\
N -- N -- N
refs/heads/dependabot/maven/v3/de.agilecoders.wicket.webjars-wicket-webjars-4.0.4
(64f05cd404)
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:
bom/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
