[Snyk] Fix for 3 vulnerabilities

[samawad]

Snyk has created this PR to fix 3 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 multiple high-risk version jumps, most notably for actionpack (Rails) and rack. The leap from ActionPack 2.3.8 to 5.0.0 spans three major Rails versions (3, 4, and 5), introducing a vast number of significant breaking changes that require a complete application overhaul. The rack upgrade from 1.1.0 to 2.2.19 also crosses a major version boundary with breaking API changes.

Top Breaking Changes:

• actionpack 2.3.8 → 5.0.0 (high): This is a monumental upgrade equivalent to migrating from Rails 2.3 to Rails 5.0. It requires fundamental architectural changes, including a new routing system, the introduction of Bundler for gem management, the shift to "Strong Parameters" from attr_accessible, and a new application model structure.
• rack 1.1.0 → 2.2.19 (medium): This major version upgrade introduces breaking changes to the Rack SPEC. Key changes include how streaming bodies are handled, requirements for request environment keys to be strings, and modifications to response headers and status codes.

Other Upgrades:

• merb 1.1.0 → 1.1.1 (low): This is a patch update for a library that was merged into Rails 3 and is considered archaic; no breaking changes are expected.
• rack-cache 0.5.2 → 0.5.3 (low): This is a patch update with a low likelihood of breaking changes.

Recommendation: A sequential, version-by-version upgrade is strongly advised (e.g., Rails 2.3 → 3.0 → 3.1 → ... → 5.0) to manage the complexity. Each step will require significant code refactoring, dependency updates, and thorough testing. Merging this change directly is not feasible.

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-13378928	721
	Allocation of Resources Without Limits or Throttling SNYK-RUBY-RACK-13378930	721
	Allocation of Resources Without Limits or Throttling SNYK-RUBY-RACK-13378932	721

---

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