Allow relaton v3 in the dependency range (>= 2.1.0) - #131
Merged
Merged
Conversation
The tight ~> 2.1.0 pin prevents the relaton v3 monogem (3.0.0.pre.alpha.x) from resolving anywhere relaton-cli appears in the graph, blocking the relaton-v3 / pubid-v2 stack migration. Widen the range; CI keeps testing the usual v2 resolution via the lockfile until the v3 port lands.
2 tasks done
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.
Summary
relaton-clipinsrelaton ~> 1.20.3, which excludes the relaton v3 monogem (3.0.0.pre.alpha.x) from any bundle containing relaton-cli — and metanorma depends on relaton-cli, so the whole relaton-v3 / pubid-v2 stack migration (metanorma-document 0.5.x etc.) cannot resolve.>= 1.20.3. The CLI's own CI still resolves and tests its usual v1/v2 line via its lockfile; the wider range only permits v3 where a consumer (e.g. the metanorma mainline) pins it deliberately.Test plan
gem dependencyrange change only, no code changesrelaton ~> 1.20.xstill resolves identically (upper bound unchanged in practice for existing consumers)