Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(cd): auto-tag releases twice a month #129

Merged
merged 5 commits into from
Dec 5, 2024
Merged

feat(cd): auto-tag releases twice a month #129

merged 5 commits into from
Dec 5, 2024

Conversation

alexeagle
Copy link
Contributor

Avoids the common pitfall where users have to request a release, i.e. the inevitable slack message 'hey could you cut a release with that new fix'

Relies on the repository using semver commit messages. This is already implied in this template because commitizen-tools/commitizen is installed as a commit-msg pre-commit hook.

Based on https://github.com/aspect-build/rules_lint/pull/427/files where this is already observed to be working.

Avoids the common pitfall where users have to request a release, i.e. the inevitable slack message
'hey could you cut a release with that new fix'

Relies on the repository using semver commit messages. This is already implied in this template because
commitizen-tools/commitizen is installed as a commit-msg pre-commit hook.

Based on https://github.com/aspect-build/rules_lint/pull/427/files where this is already observed to be working.
@fmeum
Copy link
Member

fmeum commented Nov 27, 2024

Could we make it so that only minor and patch releases are cut automatically? Major releases may require a compatibility_level bump and generally more care.

@alexeagle
Copy link
Contributor Author

I agree on the need for that. I don't see such an affordance in the action being used, so filed smlx/ccv#161 to see what the maintainer thinks.

I imagine this could be possible on our side by parsing the semver before/after info in variables, but smells like a layering violation.

@alexeagle
Copy link
Contributor Author

@fmeum that feature landed upstream and I've used the new output in the conditional. This now auto-releases only patch and minor.

@alexeagle alexeagle merged commit 7600a81 into main Dec 5, 2024
10 checks passed
@alexeagle alexeagle deleted the auto_tag branch December 5, 2024 15:58
alexeagle added a commit to bazel-contrib/rules_oci that referenced this pull request Dec 11, 2024
Simplifies life for maintainers a bit, ensuring we're never more than two weeks without commits getting shipped.

Downstreams bazel-contrib/rules-template#129
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.

2 participants