[Snyk] Fix for 1 vulnerabilities

[samawad]

Snyk has created this PR to fix 1 vulnerabilities in the rubygems dependencies of this project.

Snyk changed the following file(s):

• Gemfile

⚠️ Warning

Failed to update the Gemfile.lock, please update manually before merging.

---

This upgrade contains a major version jump for Rails from 3.0.9 to 5.0.0, which introduces significant breaking changes and requires substantial code and configuration updates. The upgrade for rspec-rails is minor and considered low risk.

Breaking Change Assessment: rails@3.0.9 → rails@5.0.0 [ high ]
This major version upgrade spans both Rails 4 and 5, introducing fundamental changes to security, model behavior, and testing. Direct migration is not recommended; an incremental upgrade path is advised by official documentation. [7, 8]

Highlights:

• Strong Parameters Required: The attr_accessible and attr_protected methods for mass-assignment protection have been removed. You must migrate to Strong Parameters in controllers to explicitly permit attributes. [1, 4]
• belongs_to Associations: In Rails 5, belongs_to associations are required by default. This will trigger new validation errors if the associated record is not present. [8]

Source: Rails documentation
Recommendation: A staged, incremental upgrade (e.g., 3.x → 4.2 → 5.0) is strongly advised to properly address deprecations and breaking changes. Do not merge without a thorough migration plan and extensive testing. [7, 11]

Additional upgrades: rspec-rails@2.12.2 → rspec-rails@2.13.0 (low) - This is a minor update with backward-compatible enhancements and bug fixes. [5]

Notice 🤖: This content was generated using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

---

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-RUBY-RACK-13052974	696

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

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