-
Notifications
You must be signed in to change notification settings - Fork 27
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
Auto-release new versions #39
Comments
I just found out that you can publish from the command line with |
I experimented with this in /~https://github.com/rubyatscale/use_packwerk but have found that some of the existing solutions are incomplete and don't play super nice together. One idea I had here was it would be interesting to look at the GitHub actions I used in CI would include build, lint, type check and CD would include build, tag, release, and deploy. |
This is finished, see #41 Note there are a couple of things that I think might be nice to have:
Going to close this for now. |
Steps to publish currently are:
This is a bit toilsome. Instead, it would be great to do all of this automatically each time a new (green) commit lands on main that changes the version. With a lot of gems, this would make it simpler to percolate changes throughout the ecosystem.
This applies to all gems in the
rubyatscale
org./~https://github.com/duderman/gh-gem-tag-action
This GitHub action automatically tags commits based on the gem spec. We'd likely want to fork this since this appears to be largely unmaintained. It also appears to not exit gracefully if a tag already exists, which we would want to add.
With this, we could simply bump the version and merge and viola, we would tag the commit, the release notes should be automatically generated, and we should run the publish job (I hope).
The text was updated successfully, but these errors were encountered: