This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/bundler/docs/0.12.0/faraday-2.14.1
in repository https://gitbox.apache.org/repos/asf/zeppelin-site.git
discard 70e468d75 Bump faraday from 2.12.0 to 2.14.1 in /docs/0.12.0
add 2ccbd9cd9 Add "jekyll" label to .asf.yaml (#36)
add 1d511c971 Bump js-yaml from 3.14.1 to 3.14.2 in
/.github/workflows/helium (#35)
add 791eac664 Bump uri from 0.13.1 to 0.13.3 in /docs/0.12.0 (#37)
add 0995d7e5a Bump undici from 6.19.7 to 6.23.0 in
/.github/workflows/helium (#38)
add f1e906f25 Bump faraday from 2.12.0 to 2.14.1 in /docs/0.12.0
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 (70e468d75)
\
N -- N -- N
refs/heads/dependabot/bundler/docs/0.12.0/faraday-2.14.1 (f1e906f25)
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 | 3 +++
.github/workflows/helium/package-lock.json | 24 ++++++++++++------------
docs/0.12.0/Gemfile.lock | 2 +-
3 files changed, 16 insertions(+), 13 deletions(-)
