Automate releases without a manual PR prior to release #2912
Description
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
- Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
- If you are interested in working on this issue or have submitted a pull request, please leave a comment.
- I'd be willing to implement this feature (contributing guide)
Describe the user story
I'd like to automate releases without making manual changes
- to avoid issues like this
- to avoid chore prs like
Describe the solution you'd like
Instead of hard coding three version, let's pass in the version using an ldflag via goreleaser
See https://github.com/cloudposse/atmos/blob/3a43ea01e4704705a23afae861931e07bafdfc8d/cmd/version.go#L8 (their default is 0.0.1, ours can be build or local) and https://github.com/cloudposse/atmos/blob/3a43ea01e4704705a23afae861931e07bafdfc8d/.goreleaser.yml#L27 for inspiration.
For the kustomize bundle, let's just use latest since that is already tied to the latest stable release.
Scenarios after completion
- PR merge - should result in version
dev-<7 char git ref>. - prerelease and release - results in version with same tag name
Currently above scenarios will return hard coded value from code
Here is where we currently document our current manual release pr steps
Describe the drawbacks of your solution
None
Describe alternatives you've considered
None
- This may be a duplicate or related to Automate version releases #1461