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

[spaceship] Update sinatra to 2.x (uses rack 2.x) #16776

Merged
merged 1 commit into from Jul 7, 2020

Conversation

aried3r
Copy link
Contributor

@aried3r aried3r commented Jul 7, 2020

Checklist

  • I've run bundle exec rspec from the root directory to see all new and existing tests pass
  • I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
  • I've read the Contribution Guidelines
  • I've updated the documentation if necessary.

Motivation and Context

The sinatra usage in this project is easy enough that it didn't need any changes when updating. While being on the latest release should be reason enough, there is one nice thing implicitly done here (not shown since no Gemfile.lock is being committed), is that rack is now also at ~> 2.0, which receives updates and security fixes (although most were backported to 1.6.x).

Description

No real description, but some CHANGELOG.md files to see what changed.

https://github.com/sinatra/sinatra/blob/master/CHANGELOG.md
https://github.com/rack/rack/blob/master/CHANGELOG.md

Example of a backported CVE fix.
https://nvd.nist.gov/vuln/detail/CVE-2019-16782

The sinatra usage in this project is easy enough that it didn't need any
changes when updating. While being on the latest release should be
reason enough, there is one nice thing implicitly done here (not shown
since no `Gemfile.lock` is being committed), is that `rack` is now also
at `~> 2.0`, which receives updates and security fixes (although most
were backported to 1.6.x).

https://github.com/sinatra/sinatra/blob/master/CHANGELOG.md
https://github.com/rack/rack/blob/master/CHANGELOG.md

Example of a backported CVE fix.
https://nvd.nist.gov/vuln/detail/CVE-2019-16782
Copy link
Member

@joshdholtz joshdholtz left a comment

Choose a reason for hiding this comment

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

TIL that fastlane has sinatra as a development dependency 🙃

Thanks for upping this, though! Appreciate the contribution ❤️

@joshdholtz joshdholtz merged commit d645590 into fastlane:master Jul 7, 2020
@fastlane-bot
Copy link

Hey @aried3r 👋

Thank you for your contribution to fastlane and congrats on getting this pull request merged 🎉
The code change now lives in the master branch, however it wasn't released to RubyGems yet.
We usually ship about once a week, and your PR will be included in the next one.

Please let us know if this change requires an immediate release by adding a comment here 👍
We'll notify you once we shipped a new release with your changes 🚀

Copy link

@fastlane-bot fastlane-bot left a comment

Choose a reason for hiding this comment

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

Congratulations! 🎉 This was released as part of fastlane 2.151.0 🚀

minuscorp pushed a commit to minuscorp/fastlane that referenced this pull request Jul 18, 2020
The sinatra usage in this project is easy enough that it didn't need any
changes when updating. While being on the latest release should be
reason enough, there is one nice thing implicitly done here (not shown
since no `Gemfile.lock` is being committed), is that `rack` is now also
at `~> 2.0`, which receives updates and security fixes (although most
were backported to 1.6.x).

https://github.com/sinatra/sinatra/blob/master/CHANGELOG.md
https://github.com/rack/rack/blob/master/CHANGELOG.md

Example of a backported CVE fix.
https://nvd.nist.gov/vuln/detail/CVE-2019-16782
@fastlane fastlane locked and limited conversation to collaborators Sep 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants