Skip to content

Conversation

@Fryguy
Copy link
Contributor

@Fryguy Fryguy commented Apr 5, 2022

If passed bundler: 2.2, setup-ruby would install bundler 2.3, because
it would generate a constraint that looks like ~> 2.2. This
unexpectedly installs the latest of the 2.x series, but the expectation
is that it would install the latest of the 2.2.x series.

Fixes #304

@Fryguy
Copy link
Contributor Author

Fryguy commented Apr 5, 2022

This PR also has the dist.js updated. I wasn't sure what your PR pattern is in this repo, so if this is wrong, let me know and I can remove that.

Copy link
Member

@eregon eregon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the PR, this looks great.

@eregon
Copy link
Member

eregon commented Apr 5, 2022

The CI seems to fail, see https://github.com/ruby/setup-ruby/runs/5836332794?check_suite_focus=true
Could you try to figure it out? A separate step before to run just bundle --version would likely be helpful.

If passed `bundler: 2.2`, setup-ruby would install bundler 2.3, because
it would generate a constraint that looks like `~> 2.2`. This
unexpectedly installs the latest of the 2.x series, but the expectation
is that it would install the latest of the 2.2.x series.

Fixes ruby#304
@Fryguy Fryguy force-pushed the fix_version_constraint branch from bf74619 to 46adeca Compare April 5, 2022 15:31
@Fryguy
Copy link
Contributor Author

Fryguy commented Apr 5, 2022

Ok, updated with the -P. Frustratingly, the original PR worked in act.

@eregon eregon merged commit 1a68550 into ruby:master Apr 5, 2022
@Fryguy Fryguy deleted the fix_version_constraint branch April 5, 2022 16:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Can't install latest bundler for a specific minor version (e.g. 2.2.x)

2 participants