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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Ruby]: Ruby / Messages bump #165
[Ruby]: Ruby / Messages bump #165
Changes from 7 commits
088ba41
c3d8f02
7189012
8e48bbc
662a09c
fa33a6f
06cdb30
2b0d261
4f589d3
6f03781
d95c74c
718e60a
326ad17
c17bc91
99f5f60
65e36f1
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As nothing materially changed about the messages for Gherkin, is there a reason not to increase the upper bound instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As in permit 19.1 but increase the upper limit to say 23?
Currently the maximum version is 22.0 so any revision in the 22.x should be fine here. Just trying to reduce the support surface area. In theory we could keep this support area the same?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. Allowing a wider range allows us to make major releases of messages without also making major releases of Gherkin.
This reduces the churn somewhat. Wouldn't worry about supported version ranges here. If something Gherkin related gets added to messages we'll have to use it in all Gherkin implementations (because of the single test suite).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean in theory nothing stops us from setting the upper limit to 30 by the same logic. Or having no upper limit.
Bundler flags things without an upper limit hence the twiddle key. In theory something could come in v23 which breaks things hence setting this value?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I would think
'>= 19.1.4', '< 23'
should be good.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll make that change now.