fix(release): revert version.rb to 0.2.5 so release workflow can bump#22
Merged
Conversation
The metanorma/ci rubygems-release workflow owns the version bump — it expects to be the one that writes the new version to lib/ea/version.rb and commits it. With the version already at 0.3.0 (committed in PR #21), the bump step is a no-op and git aborts with 'nothing to commit'. This revert returns the file to 0.2.5 so the release workflow can do its job. The actual 0.3.0 release content is already on main.
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 metanorma/ci rubygems-release workflow owns the version bump — it expects to write the new version to
lib/ea/version.rband commit it.PR #21 accidentally committed
VERSION = "0.3.0"directly, which caused the release workflow'sgit_commit "Bump ea to 0.3.0"step to abort withnothing to commit, working tree clean.This revert returns the file to 0.2.5 so the release workflow can do its job. The 0.3.0 release content is already on main; only the version-file state is being reset.
After merge, retrigger the release workflow with
next_version=0.3.0.