Fix release process so it pushes gems to RubyGems#334
Merged
jamis merged 2 commits intomongodb:masterfrom Jul 23, 2024
Merged
Conversation
comandeo-mongo
approved these changes
Jul 23, 2024
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
2 participants
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 automated release process is currently skipping the part where it actually pushes the gems it produces to RubyGems. This PR fixes that, by correcting the value that the
dry_runinput is compared against. (When passed into another action, this input is apparently converted into a string, and requires quotes. When used directly, it remains a boolean, and must not be quoted.)