ci: Install the bundle before publishing to RubyGems - #148
Merged
Merged
Conversation
The publish job ran bundle exec rake release without ever installing gems, so it failed with Could not find gem 'faraday' for both 2.7.0 and 2.8.0. Also allow a manual run so the publish can be repeated for the tag master already points at.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The rubygems-publish job runs
bundle exec rake releasebut its setup-ruby step never installed the bundle, so it fails withCould not find gem 'faraday' in locally installed gems. It failed this way for 2.7.0 in April and again for 2.8.0 just now, so the automated publish has never actually worked. Turn onbundler-cache.Also add
workflow_dispatchso the publish can be rerun by hand for the tag master already points at;rake releaseskips tagging when the tag exists at HEAD.