You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Summary
- restore `.changeset` after the empty-changeset prune so GoReleaser
does not see a dirty checkout
- allow alpha release recovery when the matching `v<version>` tag
already exists on a previous main commit but the Go release/image still
need completion
- check out an existing Go release tag before running GoReleaser, so the
partial `v0.1.0-alpha.3` state can be completed from the tagged commit
## Validation
- corepack pnpm nx test @zitadel/cli --
tests/unit/scripts/release-alpha-train.test.ts
tests/unit/scripts/check-alpha-release-plan.test.ts
- corepack pnpm run check -- --only release
- node scripts/release-alpha-train.mjs status --published false --remote
false
- git diff --check
## Release notes / changeset
- Added an empty changeset:
`.changeset/fix-alpha-goreleaser-dirty-state.md`
## Notes
- Run 27446357094 published all public npm packages at 0.1.0-alpha.3 and
pushed `v0.1.0-alpha.3`, then GoReleaser failed because pruned empty
changesets left the checkout dirty.
- The current recovery probe from this branch reports `tag_exists=true`,
`create_tag=false`, and `run_goreleaser=true` while HEAD is newer than
`v0.1.0-alpha.3`.
0 commit comments