Overview - Zitadel/zitadel

zitadel/zitadel

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
main
3afa6a2e docs: correct "complement" flow names (#11320) # Which Problems Are Solved As part of the naming inconsistencies (#5888) we want to ensure action v1 flow name are always correct and mapping to enum values line up: #11309 # How the Problems Are Solved Rename last "Customize SAML Response" occurrences to "Complement SAML Response" where it's referring to the flow type. There are some titles left with "customize SAML / OIDC response", which refer to the intent of customizing the outcome and not directly to the flow type. # Additional Changes None # Additional Context - closes 11309
33 minutes ago by yonas
Succeeded
main
267f2049 Merge 686de9996788f24b77f555b19adf7bfdd66644b3 into 4b5d6e39e195ecefb8b5382e3d2460ef70d6a980
1 hour ago by pull[bot]
Succeeded
main
686de999 fix(cmd/build): populate date variable when not set through ldflags (#11316) # Which Problems Are Solved When building zitadel through `go build` or using an IDE debugging tool, ldflags are not passed by dedault. In the past this was taken care of by the `make compile` command, which got replaced by NX. The `nx @zitadel/api:build` command does not set the ldflags either. Only the `pack-platform` command does. Because the ldflags aren't passed, the `date` and other variables remain empty in the `cmd/build` package. During init of the package, if the `version` is empty it defaults to the `date` variable. When the `date` field was empty, the parsed `dateTime` would default to `time.Now()`, but the `date` variable remained empty, resulting in a empty version. A consistently empty version string prevents upgrades of projections on dev systems, as the version from the last run is used. # How the Problems Are Solved If date failed to parse and `dateTime` is set to Now, use the formated string of `dateTime` as `date`. # Additional Context - Blocks https://github.com/zitadel/zitadel/pull/11239
1 hour ago by pull[bot]
Succeeded
main
14 hours ago
Succeeded
main
686de999 fix(cmd/build): populate date variable when not set through ldflags (#11316) # Which Problems Are Solved When building zitadel through `go build` or using an IDE debugging tool, ldflags are not passed by dedault. In the past this was taken care of by the `make compile` command, which got replaced by NX. The `nx @zitadel/api:build` command does not set the ldflags either. Only the `pack-platform` command does. Because the ldflags aren't passed, the `date` and other variables remain empty in the `cmd/build` package. During init of the package, if the `version` is empty it defaults to the `date` variable. When the `date` field was empty, the parsed `dateTime` would default to `time.Now()`, but the `date` variable remained empty, resulting in a empty version. A consistently empty version string prevents upgrades of projections on dev systems, as the version from the last run is used. # How the Problems Are Solved If date failed to parse and `dateTime` is set to Now, use the formated string of `dateTime` as `date`. # Additional Context - Blocks https://github.com/zitadel/zitadel/pull/11239
20 hours ago by mdarii
Succeeded
main
0e360d60 Merge 686de9996788f24b77f555b19adf7bfdd66644b3 into 4b5d6e39e195ecefb8b5382e3d2460ef70d6a980
22 hours ago by pull[bot]
Succeeded
main
686de999 fix(cmd/build): populate date variable when not set through ldflags (#11316) # Which Problems Are Solved When building zitadel through `go build` or using an IDE debugging tool, ldflags are not passed by dedault. In the past this was taken care of by the `make compile` command, which got replaced by NX. The `nx @zitadel/api:build` command does not set the ldflags either. Only the `pack-platform` command does. Because the ldflags aren't passed, the `date` and other variables remain empty in the `cmd/build` package. During init of the package, if the `version` is empty it defaults to the `date` variable. When the `date` field was empty, the parsed `dateTime` would default to `time.Now()`, but the `date` variable remained empty, resulting in a empty version. A consistently empty version string prevents upgrades of projections on dev systems, as the version from the last run is used. # How the Problems Are Solved If date failed to parse and `dateTime` is set to Now, use the formated string of `dateTime` as `date`. # Additional Context - Blocks https://github.com/zitadel/zitadel/pull/11239
22 hours ago by pull[bot]
Succeeded
main
23 hours ago
Succeeded
main
686de999 fix(cmd/build): populate date variable when not set through ldflags (#11316) # Which Problems Are Solved When building zitadel through `go build` or using an IDE debugging tool, ldflags are not passed by dedault. In the past this was taken care of by the `make compile` command, which got replaced by NX. The `nx @zitadel/api:build` command does not set the ldflags either. Only the `pack-platform` command does. Because the ldflags aren't passed, the `date` and other variables remain empty in the `cmd/build` package. During init of the package, if the `version` is empty it defaults to the `date` variable. When the `date` field was empty, the parsed `dateTime` would default to `time.Now()`, but the `date` variable remained empty, resulting in a empty version. A consistently empty version string prevents upgrades of projections on dev systems, as the version from the last run is used. # How the Problems Are Solved If date failed to parse and `dateTime` is set to Now, use the formated string of `dateTime` as `date`. # Additional Context - Blocks https://github.com/zitadel/zitadel/pull/11239
23 hours ago by pull[bot]
Succeeded
main
6d8f81a6 Merge 686de9996788f24b77f555b19adf7bfdd66644b3 into 4b5d6e39e195ecefb8b5382e3d2460ef70d6a980
23 hours ago by pull[bot]
Succeeded
main
4b5d6e39 chore: update js-yaml (#11300) # Which Problems Are Solved Fixes [Dependency Security Alert](https://github.com/zitadel/zitadel/security/dependabot/379) # How the Problems Are Solved This PR adds a pnpm override to force `js-yaml@^4` to resolve to `>=4.1.1`, which contains the fix for the prototype pollution vulnerability. The override only affects the 4.x line, leaving 3.x versions unchanged. # Additional Context - Closes https://github.com/zitadel/zitadel/security/dependabot/379
23 hours ago by yonas
Succeeded
main
686de999 fix(cmd/build): populate date variable when not set through ldflags (#11316) # Which Problems Are Solved When building zitadel through `go build` or using an IDE debugging tool, ldflags are not passed by dedault. In the past this was taken care of by the `make compile` command, which got replaced by NX. The `nx @zitadel/api:build` command does not set the ldflags either. Only the `pack-platform` command does. Because the ldflags aren't passed, the `date` and other variables remain empty in the `cmd/build` package. During init of the package, if the `version` is empty it defaults to the `date` variable. When the `date` field was empty, the parsed `dateTime` would default to `time.Now()`, but the `date` variable remained empty, resulting in a empty version. A consistently empty version string prevents upgrades of projections on dev systems, as the version from the last run is used. # How the Problems Are Solved If date failed to parse and `dateTime` is set to Now, use the formated string of `dateTime` as `date`. # Additional Context - Blocks https://github.com/zitadel/zitadel/pull/11239
23 hours ago by pull[bot]
Succeeded
main
1eee79a3 Merge 686de9996788f24b77f555b19adf7bfdd66644b3 into 4b5d6e39e195ecefb8b5382e3d2460ef70d6a980
23 hours ago by pull[bot]
Succeeded
main
4b5d6e39 chore: update js-yaml (#11300) # Which Problems Are Solved Fixes [Dependency Security Alert](https://github.com/zitadel/zitadel/security/dependabot/379) # How the Problems Are Solved This PR adds a pnpm override to force `js-yaml@^4` to resolve to `>=4.1.1`, which contains the fix for the prototype pollution vulnerability. The override only affects the 4.x line, leaving 3.x versions unchanged. # Additional Context - Closes https://github.com/zitadel/zitadel/security/dependabot/379
1 day ago by pull[bot]
Succeeded
main
eb856c55 Merge 4b5d6e39e195ecefb8b5382e3d2460ef70d6a980 into 62818d1b4f9adce30d2bdd3503be50205260778a
1 day ago by pull[bot]
Succeeded
main
686de999 fix(cmd/build): populate date variable when not set through ldflags (#11316) # Which Problems Are Solved When building zitadel through `go build` or using an IDE debugging tool, ldflags are not passed by dedault. In the past this was taken care of by the `make compile` command, which got replaced by NX. The `nx @zitadel/api:build` command does not set the ldflags either. Only the `pack-platform` command does. Because the ldflags aren't passed, the `date` and other variables remain empty in the `cmd/build` package. During init of the package, if the `version` is empty it defaults to the `date` variable. When the `date` field was empty, the parsed `dateTime` would default to `time.Now()`, but the `date` variable remained empty, resulting in a empty version. A consistently empty version string prevents upgrades of projections on dev systems, as the version from the last run is used. # How the Problems Are Solved If date failed to parse and `dateTime` is set to Now, use the formated string of `dateTime` as `date`. # Additional Context - Blocks https://github.com/zitadel/zitadel/pull/11239
1 day ago by muhlemmer
Succeeded
main
1 day ago
Succeeded
main
4b5d6e39 chore: update js-yaml (#11300) # Which Problems Are Solved Fixes [Dependency Security Alert](https://github.com/zitadel/zitadel/security/dependabot/379) # How the Problems Are Solved This PR adds a pnpm override to force `js-yaml@^4` to resolve to `>=4.1.1`, which contains the fix for the prototype pollution vulnerability. The override only affects the 4.x line, leaving 3.x versions unchanged. # Additional Context - Closes https://github.com/zitadel/zitadel/security/dependabot/379
2 days ago by pull[bot]
Succeeded
main
b192c196 Merge 4b5d6e39e195ecefb8b5382e3d2460ef70d6a980 into 20b6c9869af1454f6258a72d35454b7d99280b0d
2 days ago by pull[bot]
Succeeded
main
4b5d6e39 chore: update js-yaml (#11300) # Which Problems Are Solved Fixes [Dependency Security Alert](https://github.com/zitadel/zitadel/security/dependabot/379) # How the Problems Are Solved This PR adds a pnpm override to force `js-yaml@^4` to resolve to `>=4.1.1`, which contains the fix for the prototype pollution vulnerability. The override only affects the 4.x line, leaving 3.x versions unchanged. # Additional Context - Closes https://github.com/zitadel/zitadel/security/dependabot/379
2 days ago by pull[bot]