Skip to content
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

Fix compatibility with both Ruby 2.7 and Ruby 3.0 #439

Merged
merged 3 commits into from
Mar 22, 2023
Merged

Conversation

legal90
Copy link
Collaborator

@legal90 legal90 commented Mar 22, 2023

legal90 added 3 commits March 22, 2023 11:02
It is not included in Ruby 3.0 standard lib anymore, so we should add it explicitly
Vagrant 2.3.* is still using Ruby 2.7 as the embedded ruby interpreter. We should not include a strict "required_ruby_version"
in our gemfile, otherwise it won't be possible to install our plugin on Vagrant 2.3* or older.
It's better to remove the line completely and rely on the compatibility defined by the upstream Vagrant.
- Pin `vagrant` to the latest release tag `v2.3.4`. Current `main` branch has unreleased changes which brakes our
acceptance tests. Ref: hashicorp/vagrant#13052 (comment)

- Pin `vagrant-spec` to a PR branch, which contains the fix for Ruby 3.0 runtime:
hashicorp/vagrant-spec#56
@legal90 legal90 merged commit 5faf02d into master Mar 22, 2023
@legal90 legal90 deleted the fix-older-ruby branch March 22, 2023 14:51
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.

1 participant