Overview - Zitadel/zitadel

zitadel/zitadel

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
next
288f064e fix(api): check permission based on provided data on user update # Which Problems Are Solved User are allowed to change their own data including email and phone. However, they were unintentionally able to also set them to verified without according permission. # How the Problems Are Solved Fix self-management of email and phone and disallow setting them to verified without according permission. # Additional Changes None # Additional Context - requires backport to v4.x and v3.x (cherry picked from commit 0261536243e500dccfd8c7f547d592c822478327)
12 hours ago by livio-a
Succeeded
main
02615362 Merge commit from fork
12 hours ago by livio-a
Succeeded
main
b2532e96 Merge commit from fork * Inject DenyList from config to `StartCommands()` * Implementation draft * Move address checker to separate package * Migrate usages of actions.AddressChecker to denylist.AddressChecker * Rename denylist package files * Pass []denylist.AddressChecker to StartCommand * Add DenyList to defaults.yaml and add custom config parser * net: add HostnameToIPList function * denylist: Add IsHostBlocked() * actions: use denylist.IsHostBlocked() * command: Inject ip lookup function + extend add target validationt test * command: Unexport ChangeTarget.IsValid() * command: Add denyList check on ChangeTarget validation * command: Export ActionsV2DenyList and IPLookupFunction params * Lint fix * Check denylist during action execution * Fix integration tests * Apply suggestions * Add `mapstructure.StringToSliceHookFunc()` to decode `HTTPConfigDecodeHook`
12 hours ago by livio-a
Succeeded
user_table
9ce99d84 fix test
2 days ago by livio-a
Succeeded
user_table
9ce99d84 Merge f6a7616a5fc7e19def40c1803741ddafc1b44a8c into 40c7b38ca156fd83d473935f8caba9bddabfa02b
2 days ago by livio-a
Succeeded
user_table
147cfa0f docs: saas use-case - update project settings description for clarity (#11665) # Which Problems Are Solved The Project Settings section of the [/docs/guides/solution-scenarios/saas](https://zitadel.com/docs/guides/solution-scenarios/saas#project-settings) page refers to a setting `PROJECT.ROLE.CHECK` that got renamed ([1](https://github.com/zitadel/zitadel/blob/00f7dbe875606486a183f88c77497db9576e7cf5/console/src/assets/i18n/en.json#L1209), [2](https://github.com/zitadel/zitadel/blob/0f2a349ec145fc3efe0ec45db52d1f974fa180d2/console/src/assets/i18n/en.json#L2138), [3](https://github.com/zitadel/zitadel/blob/7e11f7a03279655366ab47909fd8b20151abc215/console/src/assets/i18n/en.json#L2138)). Also, the meaning of the setting was inverted on [93a4ed8 ](https://github.com/zitadel/zitadel/commit/93a4ed8857a63b24db56d17626827c662beb7579#diff-c44c61daf06a171a97f8897c96f831a54e677759198a7f2bb65ec52473a20063R36) before: "if you want to restrict access to users that have the correct authorization for the project" after: "if you want to restrict access to users that **do not** have the correct access for the project" <img width="669" height="168" alt="Screenshot 2026-02-23 at 10 59 54" src="https://github.com/user-attachments/assets/91454f6d-cefb-4db0-b064-391779ea3bae" /> <img width="692" height="660" alt="Screenshot 2026-02-23 at 10 59 46" src="https://github.com/user-attachments/assets/bba11870-c579-4fea-986b-0d960500cd77" /> # How the Problems Are Solved Update documentation. # Additional Changes n/a # Additional Context n/a --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
2 days ago by livio-a
Succeeded
user_table
147cfa0f Merge 8d9823d509dbd413f0804433d9f071e9dce47d11 into 40c7b38ca156fd83d473935f8caba9bddabfa02b
2 days ago by livio-a
Succeeded
integration-test-cov
4411e999 Update apps/api/project.json Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
2 days ago by livio-a
Succeeded
integration-test-cov
4411e999 Merge 9fb218bb4ed1a2c1dccd037113fcedeadc1c390d into 40c7b38ca156fd83d473935f8caba9bddabfa02b
2 days ago by livio-a
Succeeded
integration-test-cov
ac65e345 chore: fix integration test coverage
2 days ago by livio-a
Succeeded
integration-test-cov
ac65e345 Merge 1eaf66420ab4c5cae215935f2f348634ac79b598 into 6150a6121605c807e644dce3d37d632c62d83d9d
2 days ago by livio-a
Failed
user_table-cov
21e3de34 chore: fix integration test coverage
2 days ago by livio-a
Failed
user_table-cov
525fb1d5 chore: fix integration test coverage
2 days ago by livio-a
Succeeded
main
71fab2e5 feat: allow adding trusted domains in instance setup (#11169) # Which Problems Are Solved When running Zitadel behind a reverse proxy and especially when the API and the login UI don't run on the same domain, Zitadel needs to be configured to trust the corresponding domains and use them in public responses, like email links and more. This can be done by adding a trusted domain. However it's currently only possible through the API and not in the instance setup process. # How the Problems Are Solved Added a possibility to configure multiple trusted domains in the first instance setup process. # Additional Changes None # Additional Context - closes #11153
2 days ago by livio-a
Succeeded
invite-code
92e5e2b2 Merge fe998f5f8be89f650272bfda79043fc8d9f637da into df8824e16c4163572766f34486842dd903857217
5 days ago by livio-a
Succeeded
invite-code
92e5e2b2 re-trigger docs
5 days ago by livio-a
Succeeded
invite-code
bc85326b re-trigger docs
5 days ago by livio-a
Succeeded
invite-code
bc85326b Merge 0758eb14b7762ecabd1c0382ff180164e03f2d8e into df8824e16c4163572766f34486842dd903857217
5 days ago by livio-a
Succeeded
invite-code
eed91d84 fix: allow creating new invite code before previous is invalid
5 days ago by livio-a
Succeeded
invite-code
eed91d84 Merge 19988a5b17fdcac0de8622cddfee3f6207d7a9b1 into 1a2c2d3183c3d410e3123f41aa51946b713abe1e
5 days ago by livio-a