Skip to content

Batch daily maintenance releases with native GoReleaser - #139

Open
rb3ckers wants to merge 1 commit into
mainfrom
auto-maintenance-releases
Open

rb3ckers wants to merge 1 commit into
mainfrom
auto-maintenance-releases

Conversation

@rb3ckers

Copy link
Copy Markdown
Contributor

Batch dependency/compiler changes into daily patch releases, with manual patch/minor/major selection and retries of unpublished tags, following sts-toolbox. Publication requires successful CI for the selected commit and keeps the existing GitHub/S3 artifacts and LATEST_VERSION update.

Run the first release manually after merge because the publication configuration changed.

Validation: 36 release tests, Go tests, golangci-lint, GoReleaser check, Zizmor and Jactionlint. Live publication remains to be verified after merge.

Fixes #138

Port the sts-toolbox release selector and retry flow to sts-backup. Require successful main CI for the fixed release commit, retaining license and artifact security verification. Select the GoReleaser version validated by that commit rather than the toolbox container builder.

Keep existing S3 archives and the post-publication LATEST_VERSION update. Manual release selection is required for application and packaging changes; unpublished tags block newer releases until recovered.
if commands(before) != commands(after):
application.append(path)
elif RELEASER.findall(before) != RELEASER.findall(after):
maintenance = True

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[P2] Detect release build environment changes

This comparison ignores build-affecting environment changes. Adding GOFLAGS: -trimpath to release.yml returns (False, []); alongside a go.sum update it returns (True, []), permitting automatic publication despite the manual-release rule for packaging changes. Include build environment changes in classification and add a regression test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Batch automatic maintenance releases using the sts-toolbox flow

2 participants