This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/github_actions/github-actions-dependencies-3c815a503c
in repository https://gitbox.apache.org/repos/asf/shiro.git
omit 6ba54a18e chore(deps): bump the github-actions-dependencies group
across 1 directory with 2 updates
omit 1a27efdd1 bugfix: Enable JSR-250 `@PermitAll`, etc. annotations in
Jax-RS module - fixed inverted disabling logic
omit 5084e2bb1 chore(.asf.yaml): branch protection again
omit 54c33978a chore(.asf.yaml): branch protection again
omit d5bf2249e chore(asf.yaml): fix shiro-private name
omit 49cd83b29 chore(asf): another asf.yaml fix
add 4f8532aab chore(deps): bump the github-actions-dependencies group
across 1 directory with 2 updates
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 (6ba54a18e)
\
N -- N -- N
refs/heads/dependabot/github_actions/github-actions-dependencies-3c815a503c
(4f8532aab)
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 | 2 +-
.../java/org/apache/shiro/web/jaxrs/ShiroAnnotationFilterFeature.java | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
