This is an automated email from the ASF dual-hosted git repository.
rombert pushed a change to branch issue/SLING-12999
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-auth-oauth-client.git
omit 6a28343 SLING-12999 - Invalid refresh tokens are not cleared
add b4ac79c chore: work around testcontainers-java incompatibility with
Docker 29.0.0 (#36)
add 9cb898d SLING-12999 - Invalid refresh tokens are not cleared
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 (6a28343)
\
N -- N -- N refs/heads/issue/SLING-12999 (9cb898d)
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:
pom.xml | 11 +++++++++++
1 file changed, 11 insertions(+)
