-
Notifications
You must be signed in to change notification settings - Fork 23
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
Conversation
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.
Could we make it so that only minor and patch releases are cut automatically? Major releases may require a |
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. |
@fmeum that feature landed upstream and I've used the new output in the conditional. This now auto-releases only patch and minor. |
Simplifies life for maintainers a bit, ensuring we're never more than two weeks without commits getting shipped. Downstreams bazel-contrib/rules-template#129
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.