website/docs: fix missing breaking entry for 2025.2 release notes #13223
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Jens Langhammer <jens@goauthentik.io>
|
/cherry-pick version-2025.2 |
✅ Deploy Preview for authentik-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for authentik-storybook canceled.
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## main #13223 +/- ##
==========================================
- Coverage 92.71% 92.65% -0.07%
==========================================
Files 792 792
Lines 40231 40231
==========================================
- Hits 37301 37275 -26
- Misses 2930 2956 +26
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
tanberry
reviewed
Feb 24, 2025
tanberry
reviewed
Feb 24, 2025
| @@ -13,6 +13,12 @@ slug: "/releases/2025.2" | |||
|
|
|||
| ## Breaking changes | |||
|
|
|||
| - **Fixed behaviour in Source stage <span class="badge badge--primary">Enterprise</span>** | |||
|
|
|||
| In previous versions, the Source stage would incorrectly continue with the initial flow after returning from the source, which didn't match the documented behaviour. | |||
There was a problem hiding this comment.
What exactly does "returning from the source" mean"? Does this mean after retrieving credentials for authz from the source, or...?
There was a problem hiding this comment.
after the source redirects back to authentik
There was a problem hiding this comment.
OK, LGTM, I think most will understand it but I need to learn more.
Co-authored-by: Tana M Berry <tanamarieberry@yahoo.com> Signed-off-by: Jens L. <jens@beryju.org>
gcp-cherry-pick-bot bot
pushed a commit
that referenced
this pull request
Feb 24, 2025
…3223) * website/docs: fix missing breaking entry for 2025.2 release notes Signed-off-by: Jens Langhammer <jens@goauthentik.io> * Update website/docs/releases/2025/v2025.2.md Co-authored-by: Tana M Berry <tanamarieberry@yahoo.com> Signed-off-by: Jens L. <jens@beryju.org> --------- Signed-off-by: Jens Langhammer <jens@goauthentik.io> Signed-off-by: Jens L. <jens@beryju.org> Co-authored-by: Tana M Berry <tanamarieberry@yahoo.com>
BeryJu
added a commit
that referenced
this pull request
Feb 24, 2025
…erry-pick #13223) (#13224) website/docs: fix missing breaking entry for 2025.2 release notes (#13223) * website/docs: fix missing breaking entry for 2025.2 release notes * Update website/docs/releases/2025/v2025.2.md --------- Signed-off-by: Jens Langhammer <jens@goauthentik.io> Signed-off-by: Jens L. <jens@beryju.org> Co-authored-by: Jens L. <jens@goauthentik.io> Co-authored-by: Tana M Berry <tanamarieberry@yahoo.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Details
see #12875
Checklist
ak test authentik/)make lint-fix)If an API change has been made
make gen-build)If changes to the frontend have been made
make web)If applicable
make website)