[Snyk] Fix for 3 vulnerabilities #20
Open
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.
Snyk has created this PR to fix 3 vulnerabilities in the rubygems dependencies of this project.
Snyk changed the following file(s):
spec/rails_root/Gemfile
This upgrade from Rails 3.2.13 to 5.0.0 is a major undertaking with significant breaking changes across two major versions. It requires a new minimum Ruby version and introduces fundamental shifts in application architecture, including the mandatory adoption of Strong Parameters and changes to Active Record behavior. The upgrade from rspec-rails 2.13.0 to 2.13.1 is a minor patch with no breaking changes.
Rails 3.2.13 → 5.0.0 (high-risk):
This is a substantial upgrade spanning both Rails 4.0 and 5.0, introducing numerous breaking changes that require significant code and configuration modifications.
Highlights:
attr_accessible
andattr_protected
are removed. Mass assignment protection must be migrated to the strong parameters pattern in controllers.belongs_to
associations are required by default, which may cause validation failures where they were previously optional. Additionally, all models must now inherit fromApplicationRecord
instead ofActiveRecord::Base
.Recommendation: A sequential upgrade (first to the latest 4.2.x, then to 5.0) is strongly advised to manage the changes incrementally. Allocate significant time for code refactoring and thorough testing.
rspec-rails 2.13.0 → 2.13.1 (low-risk):
This is a patch release containing only bug fixes and no breaking API changes.
Vulnerabilities that will be fixed with an upgrade:
SNYK-RUBY-RACK-13378928
SNYK-RUBY-RACK-13378930
SNYK-RUBY-RACK-13378932
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Allocation of Resources Without Limits or Throttling