Overview - Zitadel/zitadel

zitadel/zitadel

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
fix/no-smtp-double-create
4db6cf71 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>
2 days ago by Ramon
Succeeded
fix/no-smtp-double-create
4db6cf71 Merge a2b3fbb7f2a498215c89aa1483129147759e8a07 into 0945195f68da3a11fefc3b08e4fdf47187fbe276
2 days ago by Ramon
Succeeded
fix/no-smtp-double-create
2 days ago
Succeeded
fix/no-smtp-double-create
767ac79f feat(telemetry): unify request details (#11509) # Which Problems Are Solved In the "new" structured logging, request details were added in different middlewares, such as request, instance and user IDs. This meant the the upstream request logging middleware did not have access to metadata that got added later, resulting in incomplete logs. Furthermore it was not possible to correlate an API error response to log output. # How the Problems Are Solved A mutable request details object is added to the context early on. When the api authz function run, the instance and user IDs are added to this object as they become available. Every logline emitted after this (time-wise) will then all contain these details under the `request` log group. <details> <summary>example output in JSON</summary> ```json { "time": "2026-03-13T19:21:20.890428806Z", "level": "INFO", "source": { "function": "github.com/zitadel/zitadel/internal/api/grpc/server/connect_middleware.LogHandler.func1.1", "file": "/workspaces/zitadel/internal/api/grpc/server/connect_middleware/log_interceptor.go", "line": 34 }, "msg": "request served", "request": { "id": "d6q67c04vtjmi77cbbpg", "instance_host": "localhost:8080", "instance_id": "362349751439458307", "user_id": "362349751440048131" }, "TraceID": "a9e0fee3522224f3583bbdcda737f4b4", "SpanID": "a563056eee36920a", "stream": "request", "version": "2026-03-13T19:20:59Z", "protocol": "connect", "service": "zitadel.user.v2.UserService", "http_method": "POST", "path": "/zitadel.user.v2.UserService/ListUsers", "code": "code_0", "duration": 12254350 } ``` </details> Request IDs are now also returned with a response header or metadata. Depending on the protocol: - HTTP calls always return the request ID as header, regardless of status - gRPC calls always return the request ID as header, even if there was an error - connect RPC calls returns the request ID as header on success, trailer in case of error. This is because header must be set on the response object, which is nil in case of error. When there is an error, metadata can be added which are then sent as trailers. # Additional Changes - Use the existing call duration middleware for both request ID and logging for a consistent request start timestamp in all layers. - Upgrade sloggcp for some fixes (notably TraceID) - Modify the NoCache middleware so it uses `SetHeaders` instead of `SendHeaders`. The latter prevented any other handler from setting headers, including the new request ID middleware. # Additional Context Follow up on demo of: - https://github.com/zitadel/zitadel/pull/11159 - https://github.com/zitadel/zitadel/pull/11435 - backport to v4 --------- Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com> Co-authored-by: muhlemmer <5411563+muhlemmer@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Co-authored-by: Marco A. <marco@zitadel.com>
18 days ago by Tim Möhlmann
Succeeded
fix/no-smtp-double-create
767ac79f Merge a6c6c67d71b80f5987885a691990438cac2fedc4 into 997aa607c474f5d09a84f425cd11620ec7c356cd
18 days ago by Ramon
Succeeded
fix/no-smtp-double-create
18 days ago
Succeeded
fix/no-smtp-double-create
57699318 disallow smtp double create
18 days ago by conblem
Succeeded
fix/no-smtp-double-create
57699318 Merge 6dd0d58a46e64dfca3080a30b9d633e446b962a5 into f138082b64513955466e8dddc8de2a5a1e4e6c8e
18 days ago by Ramon
Succeeded
fix/no-smtp-double-create
18 days ago