This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.ops4j.pax.tinybundles-tinybundles-4.0.1
in repository https://gitbox.apache.org/repos/asf/aries.git
discard 15069870d Bump org.ops4j.pax.tinybundles:tinybundles from 2.0.0 to
4.0.1
add edc19f79e Bump biz.aQute.bnd:bnd-maven-plugin from 3.2.0 to 6.4.0
add d5353b6b2 [MAINTENANCE] Upgrade pax tinybundles to 3.x
add 7140d8b03 [MAINTENANCE] Downgrade pax tinybundles to 2.1.1
add 9fb29eddf [MAINTENANCE] Downgrade pax tinybundles to 2.0.0 in subsystem
add 6ff5ab32f Merge pull request #569 from apache/upgrade-pax-tinybundles
add 56312b1da Bump org.ops4j.pax.tinybundles:tinybundles from 2.0.0 to
4.0.1
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 (15069870d)
\
N -- N -- N
refs/heads/dependabot/maven/org.ops4j.pax.tinybundles-tinybundles-4.0.1
(56312b1da)
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/dependabot.yaml | 5 +++++
pushstream/pom.xml | 2 +-
subsystem/subsystem-itests/pom.xml | 1 +
3 files changed, 7 insertions(+), 1 deletion(-)
