(NEW!) Zitadel V3 - Release Candidate
Hey there! 👋🏾
The release candidate for Zitadel V3 is now available, and we would greatly appreciate your feedback prior to the generally available release later on this month.
⭐ Key features & improvements coming with V3:
- Actions V2
- Discontinuation of Cockroach DB support
For a more comprehensive outline of all changes in V3, check out our dedicated epic!
Testing period: April 1st - April 30th, 2025
How to gain access to V3’s release candidate: Update your self-hosting instance to the latest version & please ensure you’re using PostgreSQL
Guide on how to migrate from Cockroach to Postgres: https://zitadel.com/docs/self-hosting/manage/cli/mirror
Limitations/bugs: No known bugs or limitations with V3 yet
Please test the latest version of Zitadel and share your feedback below. If you have any suggestions or have any bug reports to share, please create an issue on GitHub!
Thanks for your feedback! 🫶🏾
11 Replies
Unknown User•3mo ago
Message Not Public
Sign In & Join Server To View
Hello @Raccine. We are looking forward the upgrade.
Is there any plan to add a guide or practical examples on how to migrate from Actions V1 to Actions V2 together with the release of V3. Something similar like the actions marketplace repository? Thanks 🙂
Hey there! Great question - Let me double check and get back to you as soon as possible ☺️
Hey @Arnau! There's actually a sub-issue that exists for adding documentation regarding migrating from actions v1 to actions v2! You can take a look at the sub-issue and its current status here: https://github.com/zitadel/zitadel/issues/8599?issue=zitadel%7Czitadel%7C9456
In terms of practical examples, what are some examples you would like to see based on your use case? ☺️
GitHub
ZITADEL V3 · Issue #8599 · zitadel/zitadel
This release fully integrates the new Zitadel Actions, alongside revamped task handling for improved reliability, cleaned-up APIs by removing beta versions, and streamlined database support to Post...
Cool, thanks! I see all Flow Types and Triggers we are using listed there.
Some examples we would like to see based in our use cases:
External Authentication, Post Authentication:
- Set ZITADEL user firstName, lastName and email (as verified) with values from
- Retrieve
providerInfo.attributes (IdP Attributes).
- Set ZITADEL user metadata from providerInfo.attributes- Retrieve
externalUser.externalId
Complement Token, Pre access token creation:
- Call a custom POST HTTP endpoint sending the ZITADEL user id, email, and org ID, as well as some of it's metadata.
- Complement the access token with custom claims with values retrieved from the custom POST HTTP endpoint response.
Complement Token, Pre Userinfo creation
- Get ZITADEL user metadata and set custom claims.Hey there @pbechliv! Sorry for the delay in response - You should already be able to use the new login in Zitadel cloud (it's currently in beta). For more info around the hosted login, how to access it, and more - you can check out this doc here! ➡️ https://zitadel.com/docs/guides/integrate/login/hosted-login#hosted-login-version-2-beta
Let me know if you have any additional questions! :gigipixel:
ZITADEL Docs
ZITADEL provides a hosted single-sign-on page to securely sign-in users to your applications.
No problem! Thanks for sharing your feedback around the examples you would like to see - I'll share these internally and reach back out with more info if anything! :gigipixel:
Have you been able to test out the V3 release candidate yet?
Yes, even though just locally for now. I could migrate part of the External Authentication V1 Actions mentioned above to V2, looking forward to complete the rest soon following the migration docs that were released yesterday (also gave some feedback in the linked sub-issue PR).
As noted in this issue: https://github.com/zitadel/zitadel/issues/9710#issuecomment-2791760691, we are currently facing serialization issues during our migration to V2. For instance, setting a Human User Email as verified via Actions V2 doesn’t appear to work as expected.
Despite trying several combinations of camelCase and snake_case formats when handling responses, I haven’t been able to make it work reliably.
This has made the migration experience somewhat frustrating, as it often becomes a trial-and-error process. While I’ve been following the provided migration examples in the documentation, the actual payloads received by the targets don’t always match the guides — sometimes they align, but other times they diverge.
I’d really appreciate it if you could prioritize reviewing the reported issue. It would also be helpful to have more comprehensive migration examples, particularly covering 1:N scenarios, to improve the overall developer experience.
GitHub
Actions V2: serialization issues · Issue #9710 · zitadel/zitadel
While reviewing the actions v2 documentation PR, I noticed multiple issues and incosistencies in the (de)serialization of the payload of actions: The json package is used to marshal and unmarshal t...
Hi @Raccine, we upgraded our non production instance from v2.67.2 to v3.0.0-rc2 , no issues found as of now. 👍 We are now migrating our Actions to V2.
Do you guys have an ETA for the final v3.0.0 release?
Thanks!
Hey @Arnau! Thanks for your patience - I checked in with the team and it looks like the generally available release for v3 should be ready next week or so! ☺️