Repository navigation
Publish a plain gem each release - #132
Merged
Merged
Conversation
The plain-gem release and the setup error wording are release process, not user-facing behavior, so they get no changelog entries.
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
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.
Why is this change needed?
The RubyGems page lists the plain build's version as the gem's current
version. The last plain build is 0.5.0, so the page still says 0.5.0.
The generic setup error also gave every user the same advice, which is
wrong for most of them.
What does this change do?
Publish a plain, engine-less gem each release through a standalone
release job. The plain build carries a post-install message naming the
SE_LANGUAGETOOL_EXECUTABLEescape hatch. The setup error now namesthe actual failure: a missing override path, a broken platform install,
or an engine-free plain gem.