Overview - Zitadel/zitadel

zitadel/zitadel

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
administrator-repo
ae6cd662 feat: allow transactional table setup step to recreate the whole schema (#11833) ## Problem description - Setup currently creates/updates relational tables, but there is no built-in way to fully reset the relational schema during iterative development. - Re-running setup after schema/projection changes can leave stale relational objects and projection state behind, which makes local/dev validation harder. - There is no explicit, configurable switch in setup steps for destructive schema recreation behavior. ## How the Problems Are Solved - Adds a new setup step configuration section for relational tables with a `ShouldRecreateSchema` flag (default `false`). - Wires the new config flag into the transactional tables setup step. - Extends the transactional tables execution logic to optionally: - Drop the `zitadel` schema with `CASCADE` - Clean related projection state entries for relational tables in `projections.current_states` - Recreate tables through the existing setup flow afterward - Wraps the destructive operations in a transaction and keeps error/rollback handling plus logging for visibility. ## Additional Changes - Adds an explicit warning in step configuration that schema recreation is intended for development and not production use. - Keeps behavior fully backward-compatible by default (`ShouldRecreateSchema: false`), so existing setups are unchanged unless the flag is enabled. ## Additional Context - Follow-up for relational setup/dev workflow improvements. - PR: #11833 ## How to use it ### Env `export ZITADEL_RELATIONALTABLES_SHOULDRECREATESCHEMA=true` ### Config Add the following to your custom setup steps config: ```yaml RelationalTables: ShouldRecreateSchema: true ```
20 days ago by Silvan
Succeeded
administrator-repo
ae6cd662 Merge 50c2ea2a37a187b74f650081d4aaad670d90395d into 6d90a120a6f5b455f00001021d1c5abc6727a462
20 days ago by Silvan
Succeeded
administrator-repo
89ecb51f feat(login): update to nextjs 16, improve caching, change default colors (#11629) # Which Problems Are Solved Updated the project to use the latest versions of Next.js and React, and implemented a SWR caching strategy for key settings API calls to improve performance. Adjusted configuration to ensure compatibility with Next.js 16. # How the Problems Are Solved - Updated next to 16.1.6, react & react-dom to 19.2.4, and next-intl to 4.8.3. - Implemented `API_CACHE_ENABLED` and `API_CACHE_CONFIG` (replacing deprecated unstable_cacheLife) for: - getBrandingSettings - getSecuritySettings - getPasswordComplexitySettings - getLoginSettings ... - Updated default theme colors from blue to a more neutral black and white # Additional changes - Updated login docker image to node 24 --------- Co-authored-by: Ramon <mail@conblem.me>
21 days ago by Max Peintner
Failed
administrator-repo
89ecb51f feat(login): update to nextjs 16, improve caching, change default colors (#11629) # Which Problems Are Solved Updated the project to use the latest versions of Next.js and React, and implemented a SWR caching strategy for key settings API calls to improve performance. Adjusted configuration to ensure compatibility with Next.js 16. # How the Problems Are Solved - Updated next to 16.1.6, react & react-dom to 19.2.4, and next-intl to 4.8.3. - Implemented `API_CACHE_ENABLED` and `API_CACHE_CONFIG` (replacing deprecated unstable_cacheLife) for: - getBrandingSettings - getSecuritySettings - getPasswordComplexitySettings - getLoginSettings ... - Updated default theme colors from blue to a more neutral black and white # Additional changes - Updated login docker image to node 24 --------- Co-authored-by: Ramon <mail@conblem.me>
21 days ago by Max Peintner
Succeeded
administrator-repo
89ecb51f Merge ff77a77224382f979c4c2f97bc2cf8cfc50c5e1a into a864434b4b684fc6f9190453cc7484edca856ed8
21 days ago by Silvan
Succeeded
administrator-repo
bfbe6fe0 chore(login): remove integration tests (#11608) # Which Problems Are Solved Removes the Cypress integration tests and associated configuration from the apps/login project to streamline the build process. # How the Problems Are Solved - Removed cypress directory, integration directory, and cypress.config.ts from apps/login. - Updated project.json to remove test-integration targets and dependencies. - Updated package.json to remove the cypress dev dependency and clean script reference. - Updated tsconfig.json to remove the now-redundant integration exclusion. - Ensured acceptance tests are preserved and correctly excluded from build inputs. --------- Co-authored-by: Florian Forster <florian@zitadel.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: conblem <mail@conblem.me>
21 days ago by Max Peintner
Succeeded
administrator-repo
bfbe6fe0 Merge f80101ce7a59379f015e944bb84b25194ac432ec into c1be72765c551c72740907430b4bbd5b194f19f7
21 days ago by Silvan
Failed
administrator-repo
88165654 Merge commit from fork * fix: add `Scopes` to `Request` interface so that scopes can be validated on all requests * feat: assert org from scope exists when authorizing requests * fix: check all scopes * comments * check org on callback creation * fix tests * clarifications * fix scope marshaling * fix: enfore organization for authrequest in initiation * fix: filter sessions on the accounts page by organization scope * add integration tests --------- Co-authored-by: Livio Spring <livio@zitadel.com> Co-authored-by: Max Peintner <peintnerm@gmail.com>
21 days ago by Wim Van Laer
Succeeded
administrator-repo
88165654 Merge 985c33372d484d554fc73cef933b0c7d99f9cfce into c3a6bdb0bb738601f98192ffd6db83fb89f5fbc5
21 days ago by Silvan
Failed
administrator-repo
bde6dc6a docs: simplify helm chart guide (#11781) ## Summary Rewrites the Kubernetes quickstart (Stage 1) to match the simplicity of the Docker Compose quickstart. With the new bundled chart, users deploy the full stack — PostgreSQL, Traefik, ZITADEL API, ZITADEL Login — with two copy-paste blocks and no prerequisites beyond a Kubernetes cluster. ## Before / After **Before:** - Requires a pre-installed ingress controller - 4 manual steps: install PostgreSQL separately, create secrets, wire DB config, install ZITADEL - Users need to understand Helm dependency management **After:** ```bash mkdir zitadel-helm && cd zitadel-helm && curl -fsSLO https://raw.githubusercontent.com/zitadel/zitadel-charts/main/examples/0-quickstart/quickstart-values.yaml ``` ```bash helm repo add zitadel https://charts.zitadel.com && helm repo add bitnami https://charts.bitnami.com/bitnami && helm repo add traefik https://traefik.github.io/charts && helm repo update && helm upgrade --install zitadel zitadel/zitadel --values quickstart-values.yaml --wait ``` Same UX as the Docker Compose quickstart. Mirrors the GitLab chart pattern. ## Changes to `kubernetes/index.mdx` ### Stage 1 — Quickstart (full rewrite) - Prerequisites reduced to: a Kubernetes cluster (1.30+), kubectl, Helm - k3d moved to an optional callout tip (no longer required) - Install section: `mkdir` → `curl` → `helm upgrade --install --wait` (two copy-paste blocks, same pattern as compose) - `helm upgrade --install` instead of `helm install` — idempotent, safe to re-run - "Swap out components" table: shows how to replace PostgreSQL, Traefik, or add Redis - Callouts: masterkey warning, stack architecture diagram ### Stage 2+ (unchanged) Production cluster setup, TLS, cert-manager, etc. are untouched. ## Related - Chart changes PR: [zitadel/zitadel-charts#560](https://github.com/zitadel/zitadel-charts/pull/560) --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
21 days ago by Florian Fo...
Succeeded
administrator-repo
bde6dc6a Merge 546405f8fe53d0794e0ea9a59655715620cca3a9 into 3fdac54878787290c987bfcad7152e6fa522ffe2
21 days ago by Silvan
Failed
administrator-repo
1425654b review comments
22 days ago by adlerhurst
Succeeded
administrator-repo
1425654b Merge 08b48d4c96124049ca615a42db04127e3c1e2ace into cadf75e4fedf89287fc641367cd6145d7d5b60b9
22 days ago by Silvan
Succeeded
administrator-repo
bc516216 fix the config @fforootd destroyed with copilot
26 days ago by adlerhurst
Succeeded
administrator-repo
bc516216 Merge 7ae9017e1b9eeeaa7f3a01f00482c2bdb9af16f1 into cbf05dbe16d74143e95bca266965fcbd627e8278
26 days ago by Silvan
Succeeded
administrator-repo
8d4df4d9 fix the config @fforootd destroyed with copilot
26 days ago by adlerhurst
Succeeded
administrator-repo
8d4df4d9 Merge eacd78a9473aa535dcca62b6f61dfbd3dd4e3a57 into cbf05dbe16d74143e95bca266965fcbd627e8278
26 days ago by Silvan
Succeeded
administrator-repo
438b5c61 add exclusion for callReduce
26 days ago by adlerhurst
Succeeded
administrator-repo
438b5c61 Merge 603043d01b5a57af033ceeba2252c6114786e05a into cbf05dbe16d74143e95bca266965fcbd627e8278
26 days ago by Silvan
Failed
administrator-repo
523b2485 lets pray that this is the version of the linter
26 days ago by adlerhurst