This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.bouncycastle-bcprov-jdk15on-1.67
in repository https://gitbox.apache.org/repos/asf/synapse.git
discard a50eeb872 Bump bcprov-jdk15on from 1.49 to 1.67
add 490d3c1f6 Use a specific Java 8 version
add ee190a448 Bump commons-io from 2.1 to 2.7
add 07c91f87e Add .asf.yaml to configure notifications
add d0515df4b Remove unnecessary dependencies on Xerces
add 4cab331a1 Bump junit from 4.12 to 4.13.1
add 8cd53db8c Remove unused property
add ba94a28eb Update Bouncycastle to the most recent working version
add d1226d870 Bump bcprov-jdk15on from 1.49 to 1.67
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 (a50eeb872)
\
N -- N -- N
refs/heads/dependabot/maven/org.bouncycastle-bcprov-jdk15on-1.67 (d1226d870)
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:
.asf.yaml | 5 +++++
.github/workflows/build_cron.yml | 2 +-
.github/workflows/build_pull.yml | 2 +-
modules/core/pom.xml | 6 ------
modules/distribution/pom.xml | 4 ----
modules/extensions/pom.xml | 4 ----
pom.xml | 11 ++---------
7 files changed, 9 insertions(+), 25 deletions(-)
create mode 100644 .asf.yaml
