Repository navigation
chore(deps): update ghcr.io/zitadel/zitadel docker tag to v4.20.3 - #124
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/ghcr.io-zitadel-zitadel-4.x
branch
2 times, most recently
from
November 3, 2026 11:58
079fb07 to
de88f2e
Compare
renovate
Bot
force-pushed
the
renovate/ghcr.io-zitadel-zitadel-4.x
branch
from
November 9, 2026 19:49
de88f2e to
761e046
Compare
renovate
Bot
force-pushed
the
renovate/ghcr.io-zitadel-zitadel-4.x
branch
from
November 13, 2026 14:44
761e046 to
c06a6d7
Compare
This file contains hidden or 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
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.
This PR contains the following updates:
v4.19.5→v4.20.3Release Notes
zitadel/zitadel (ghcr.io/zitadel/zitadel)
v4.20.3Compare Source
CreateCallback,CreateResponse) now requires thesession.linkpermission, whatever headers are sent. The hosted Login V2 and custom login UIs whose service user has theIAM_LOGIN_CLIENTrole are not affected. If yours uses another user, for example anIAM_OWNERpersonal access token, grant itIAM_LOGIN_CLIENTbefore upgrading.x-zitadel-public-hostheader must be a single plain host with an optional port. Other values are now rejected instead of ignored.src/lib/server/andsrc/lib/actions/, and the build fails on Server Actions missing fromchecks/server-actions.allowlist.json.Error changes
No existing error IDs, message keys or gRPC codes were changed or removed. The following calls can now return errors where they previously succeeded:
CreateCallback,CreateResponse(OIDC/SAML)session.linkPERMISSION_DENIEDFAILED_PRECONDITION,Errors.Org.LoginPolicy.UsernamePasswordNotAllowedFAILED_PRECONDITION,Errors.Org.LoginPolicy.NotFoundFAILED_PRECONDITION,Errors.User.UserIDMissing(new,COMMAND-Vz4tb)/oauth/v2/token(code issued through Login V1)invalid_grantx-zitadel-public-hostheader400,invalid public host(new,HTTP-Rk7pX)4.20.3 (2026-11-13)
Bug Fixes
v4.20.2Compare Source
Bug Fixes
v4.20.1Compare Source
Bug Fixes
v4.20.0Compare Source
GODEBUG=urlstrictcolons=0orGODEBUG=tlssecpmlkem=0restores the previous behavior.ZITADEL_SESSION_COOKIE_SECRET, like the other login proofs. Users in the middle of a device authorization during the upgrade have to enter the user code again.Bug Fixes
Features
Performance Improvements
Configuration
📅 Schedule: (in timezone Asia/Shanghai)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.