-
Notifications
You must be signed in to change notification settings - Fork 3k
OIDC Token Propagation: Drop deprecated @AccessToken
annotation
#49667
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OIDC Token Propagation: Drop deprecated @AccessToken
annotation
#49667
Conversation
This comment has been minimized.
This comment has been minimized.
bba2adf
to
822b822
Compare
This comment has been minimized.
This comment has been minimized.
822b822
to
9ad2907
Compare
I think there is something wrong with the |
This comment has been minimized.
This comment has been minimized.
9ad2907
to
60eaa8c
Compare
This comment has been minimized.
This comment has been minimized.
CC @cescoffier I agree with @michalvavrik it is OK to drop the deprecated annotation now after 2 LTSs (and corresponding product releases) but CC-ing to you just in case you think we should wait for longer |
I'll open PR for the |
It is really my fault, I should had done it when I deprecated the annotation, but forgot. |
@michalvavrik Np at all, I could've checked the quickstart myself too when it was deprecated. The quickstart guide in the docs does not show the deprecated one. It is unlikely users haven't noticed they may have a deprecated annotation in their code, so we should be good to merge. I'd just like to wait a bit for Clement's input, but otherwise, given 2 main product releases have had this annotation deprecated, we should be safe to drop it |
@michalvavrik Just to double check, the current |
no, you can see it on my other PRs, they have tag 3.28. |
e.g. #49647 |
I think it's ok to drop the property. It will still require a note in the migration guide and the release notes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we check the CI issue before merging?
60eaa8c
to
fa5fbd3
Compare
I have rebased on the current main, since the QuickStart PR is merged, the PR CI should be green now. |
Status for workflow
|
Here is a proposal for the migration guide note:
If someone agrees, you can add it, or wait till Sergey is back. This shouldn't be urgent. |
…dc.token.propagation.common.AccessToken io.quarkus.oidc.token.propagation.AccessToken was deprecated since 3.19 and removed for 3.28 quarkusio/quarkus#49667
…dc.token.propagation.common.AccessToken io.quarkus.oidc.token.propagation.AccessToken was deprecated since 3.19 and removed for 3.28 quarkusio/quarkus#49667
The
io.quarkus.oidc.token.propagation.AccessToken
annotation was deprecated and marked for removal in Quarkus 3.19 in the #45923, so there were 2 LTS (3.20 and 3.27), which is why I think it is safe to drop the annotation in Quarkus 3.28.io.quarkus.oidc.client.*
packages are split across multiple modules #44736