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>
This commit is contained in:
committed by
GitHub
parent
2ba79627bc
commit
c30b7ee3e9
@ -20,6 +20,12 @@ To try out the release candidate, replace your Docker image tag with the latest
|
|||||||
|
|
||||||
## Breaking changes
|
## 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.
|
||||||
|
|
||||||
|
With this release this behaviour has been corrected and the source stage will now correctly run the selected enrollment/authentication flow before returning to the flow from which the source stage was executed.
|
||||||
|
|
||||||
- **Deprecated and frozen `:latest` container image tag after 2025.2**
|
- **Deprecated and frozen `:latest` container image tag after 2025.2**
|
||||||
|
|
||||||
Using the `:latest` tag with container images is not recommended as it can lead to unintentional updates and potentially broken setups.
|
Using the `:latest` tag with container images is not recommended as it can lead to unintentional updates and potentially broken setups.
|
||||||
|
|||||||
Reference in New Issue
Block a user