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

Support releasing without rake #3

Open
ekohl opened this issue Dec 23, 2023 · 5 comments
Open

Support releasing without rake #3

ekohl opened this issue Dec 23, 2023 · 5 comments

Comments

@ekohl
Copy link

ekohl commented Dec 23, 2023

I appreciate an action is published to make releasing easier. Standardizing the ecosystem is a good thing and I wasn't aware of rubygem-await (but have certainly it the problem it wasn't published before).

With the aim of replacing my release-gem.yml I started to play with this. In a test project I noticed this uses rake release, and then saw it was also documented in the README:

Your project has the bundler release tasks configured

My test project doesn't use rake at all and I'd like it if I didn't need to run bundle install just to publish the gem. My current workflow uses gem build and gem push. Are you open to supporting this way or should I enhance my current workflow to reuse rubygems/configure-rubygems-credentials? (I really appreciate those steps are separated for easier composability).

@segiddins
Copy link
Member

I am open to us pointing to a script file in the repo that can run build & push, but since this is such a small action, I do want to keep it focused on the most common way of releasing (which is running rake release)

@bastelfreak
Copy link

is that actually the most common way? I package many ruby gems for Arch Linux and the majority of them uses gem build and gem push in a pipeline, not any rake task.

@mschwager
Copy link

+1 for not requiring rake-release. By default, that tool attempts to create a git tag and push it. This means it's incompatible with GitHub Actions jobs that only run on tag. In other words, my ideal workflow would be kicking off the gem release job on tag, but rake-release also tries to create a tag, and subsequently fails.

@segiddins
Copy link
Member

https://github.com/rubygems/rubygems/blob/072176243027a60e20ffe6976ec59b45bc65f351/bundler/lib/bundler/gem_helper.rb#L76 by default bundler's rake task checks if the tag already exists

@mschwager
Copy link

https://github.com/rubygems/rubygems/blob/072176243027a60e20ffe6976ec59b45bc65f351/bundler/lib/bundler/gem_helper.rb#L76 by default bundler's rake task checks if the tag already exists

Ahh, good to know. Although that requires the tag to be formatted like vX.X.X, whereas I usually tag the exact semver like X.X.X. So in that case it fails to detect if the tag already exists 🤷

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 a pull request may close this issue.

4 participants