This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/transaction/transaction-manager/commons-io-commons-io-2.14.0
in repository https://gitbox.apache.org/repos/asf/aries.git
omit 6662eaeb7 Bump commons-io:commons-io in
/transaction/transaction-manager
add d13be6da9 Bump asm.version from 9.6 to 9.7.1 in /spi-fly
add 8b6872d56 [MAINTENANCE] Add transaction workflow
add 898860227 Bump commons-io:commons-io in
/transaction/transaction-manager
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 (6662eaeb7)
\
N -- N -- N
refs/heads/dependabot/maven/transaction/transaction-manager/commons-io-commons-io-2.14.0
(898860227)
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/{jmx.yml => transaction.yml} | 9 ++++-----
spi-fly/pom.xml | 2 +-
transaction/transaction-itests/pom.xml | 2 +-
3 files changed, 6 insertions(+), 7 deletions(-)
copy .github/workflows/{jmx.yml => transaction.yml} (87%)
