zitadel
Team
zitadel/zitadel
Sign in / Sign up
Open main menu
zitadel/zitadel
GitHub
Overview
Runs
Analytics
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Failed
action-v2-project-id
1ce9a7ef update integration tests
1 day ago
by mdarii
m
Succeeded
action-v2-project-id
1ce9a7ef Merge 818f0b8c952f17060cdfcde1508d61cba4242b67 into 686de9996788f24b77f555b19adf7bfdd66644b3
1 day ago
by mdarii
m
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
2 days ago
by mdarii
m
Previous page
Previous
Next
Next page