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

Get rid of the Gemfile.lock #145

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

smortex
Copy link
Member

@smortex smortex commented Jun 30, 2024

The lockfile allow reproducible build, which are awesome. However, we
also want to support multiple versions of Ruby, and a lockfile is
unfortunately not a one-size-fit-all solution in this case:

  • Older versions of bundler cannot run on recent versions of Ruby;
  • Recent versions of bundler cannot run on older versions of Ruby;
  • Some dependencies are available for some versions of Ruby but not
    all the ones we support, so a version of Ruby may be unable to run
    the bundle generated by another version of Ruby.

The lock file is only used when someone clone the repository and run
bundle install. When installing with gem install riemann-dash (the
way recommanded in the README), the dependencies only have to be in the
bounds of what is authorized in the gemspec file, so this will only
affect a fraction of our users which are probably aware of what they are
doing.

This allows us to run the test suite on all supported versions of Ruby.

The lockfile allow reproducible build, which are awesome.  However, we
also want to support multiple versions of Ruby, and a lockfile is
unfortunately not a one-size-fit-all solution in this case:

  * Older versions of bundler cannot run on recent versions of Ruby;
  * Recent versions of bundler cannot run on older versions of Ruby;
  * Some dependencies are available for some versions of Ruby but not
    all the ones we support, so a version of Ruby may be unable to run
    the bundle generated by another version of Ruby.

The lock file is only used when someone clone the repository and run
`bundle install`.  When installing with `gem install riemann-dash` (the
way recommanded in the README), the dependencies only have to be in the
bounds of what is authorized in the gemspec file, so this will only
affect a fraction of our users which are probably aware of what they are
doing.

This allows us to run the test suite on all supported versions of Ruby.
tzinfo (2.0.6)
concurrent-ruby (~> 1.0)
uri (0.13.0)
webrick (1.8.1)
Copy link
Member Author

@smortex smortex Sep 24, 2024

Choose a reason for hiding this comment

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

We just received a notification saying that this version of webrick is vulnerable to HTTP Request Smuggling:

GHSA-6f62-3596-g6w7

Getting rid of Gemfile.lock allows consumers to not depend on us for updating our dependencies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant