[Snyk] Fix for 2 vulnerabilities

[samawad]

Snyk has created this PR to fix 2 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 major version increases for sinatra (1.3.2 → 4.2.0) and rack (1.6.0 → 2.2.20), introducing significant breaking changes. The unicorn upgrade (4.8.3 → 4.9.0) is minor and carries low risk.

Highlights:

• Sinatra (1.3.2 → 4.2.0): High risk. This upgrade spans multiple major versions (2.0, 3.0, 4.0). Key breaking changes include dropping support for older Ruby versions, replacing the internal router with Mustermann, and requiring Rack 3. Many template engines like erubis and sass have been removed.
• Rack (1.6.0 → 2.2.20): High risk. The upgrade to 2.x drops support for Rack 1.x. While the target version 2.2.20 is still on the 2.x line, applications must be compatible with the initial Rack 2.0 breaking changes.
• Unicorn (4.8.3 → 4.9.0): Low risk. This is a minor version bump with no documented breaking API changes.

Recommendation: A staged migration is required. First, upgrade the application to be compatible with Sinatra 2.0 and Rack 2.0, addressing the new router and dependency requirements. Then, proceed with further incremental upgrades to reach the target versions, paying close attention to the breaking changes in Sinatra 3.0 and 4.0.

Notice 🤖: This content was generated using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.
Was this summary helpful 👍? Not helpful 👎?

---

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-RUBY-RACK-13535097	721
	Regular Expression Denial of Service (ReDoS) SNYK-RUBY-SINATRA-13535098	631

---

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
🦉 Regular Expression Denial of Service (ReDoS)