Overview - Zitadel/zitadel

zitadel/zitadel

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Failed
feat/ecdsa-ed25519-public-keys
4e7625a7 chore: deps update (#11968) # Which Problems Are Solved This pr updates major and minor dependencies and is the first step on getting our dependabot alerts cut down. # How the Problems Are Solved Depedency updates across the board eg: - Upgrade Angular to v21 - Upgrade next.js to v16.2 - Upgrade tailwind to v4 in the login - Upgrade vitest to v4 in the login This is an uncompleted list refer to the changed files for a full overview of all the updates. # Additional Changes Migrated all control flow in the console to the modern control flow syntax. Fixed the dependsOn setting for the @zitadel/login:test-unit nx target. # Additional Context - Closes https://github.com/zitadel/zitadel/issues/11274 --------- Co-authored-by: Max Peintner <peintnerm@gmail.com>
3 days ago by Ramon
Succeeded
feat/ecdsa-ed25519-public-keys
4e7625a7 Merge 0e044de73a437d923355ed018193ba6ce9671ab9 into 0945195f68da3a11fefc3b08e4fdf47187fbe276
3 days ago by Bertrand
Succeeded
feat/ecdsa-ed25519-public-keys
3 days ago
Succeeded
feat/ecdsa-ed25519-public-keys
16861f96 Merge c1ca49cf9d70028f9eb8fc89b09192fc40f90d56 into 891c7473ca222a99811a3b3e7e4d7b15d8ec6d1c
4 days ago by Bertrand
Failed
feat/ecdsa-ed25519-public-keys
16861f96 fix(login): invite flow instead of email verification for users with no primary method, improve sending behaviour (#11837) Closes #10929 # Which Problems Are Solved When a human user without a primary authentication method enters their email on the login screen, the login historically auto-sent an email code (send=true) and redirected them to the `/verify` flow. If the user was newly created via the API and already received an initial verify-email, navigating to the login page would trigger a new invite code, silently invalidating the code they received in their first email. Additionally instead of resending the same type of email (invitation) a regular email verification mail was sent # How the Problems Are Solved - Resend an invitation email instead of a email verification if a user has no method set (still in invitation state) - Conditional Code Sending: Updated `loginname.ts` to check `humanUser?.email?.isVerified`. We only auto-send a new code (`send=true`) if the user's email is already verified. Unverified users will be redirected with `send=false`, allowing them to safely enter the code they already have. - UI State Fix: Fixed an issue in `verify/page.tsx` where the send URL parameter was being checked directly as a string ("false" is truthy). By using the properly evaluated doSend boolean, the "Code Sent" alert now correctly hides itself when a new code is not explicitly sent. - Translation Updates: Refined the codeSent messaging across all locales to specify "A new code has been sent..." to provide better context to the user when they do explicitly request a resend.
4 days ago by Max Peintner
Succeeded
feat/ecdsa-ed25519-public-keys
4 days ago
Succeeded
feat/ecdsa-ed25519-public-keys
4 days ago
Succeeded
feat/ecdsa-ed25519-public-keys
e2cbf935 ci: add workflow to build and publish fork Docker image
25 days ago by bfoing
Succeeded
feat/ecdsa-ed25519-public-keys
25 days ago
Succeeded
feat/ecdsa-ed25519-public-keys
25 days ago
Succeeded
feat/ecdsa-ed25519-public-keys
25 days ago
Succeeded
feat/ecdsa-ed25519-public-keys
25 days ago