[Snyk] Fix for 1 vulnerabilities

[howardfackrell]

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.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Improper Neutralization SNYK-RUBY-ACTIVERECORD-11800112	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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[Copilot]

Pull Request Overview

This PR fixes a medium-severity security vulnerability (SNYK-RUBY-ACTIVERECORD-11800112) by upgrading Rails and related dependencies to secure versions. The changes involve major version upgrades that may introduce breaking changes.

• Updates Rails from unspecified version to >= 7.1.5.2
• Upgrades rails_admin to >= 3.0.0
• Updates sequenced to >= 3.2.0

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Using '>=' version constraint for a major version upgrade (Rails 5.x to 7.x) can introduce breaking changes unexpectedly. Consider using a more restrictive constraint like '~> 7.1.5' to prevent automatic upgrades to Rails 8.x which may have additional breaking changes.

Suggested change

	gem 'rails', '>= 7.1.5.2'
	gem 'rails', '~> 7.1.5.2'

[Copilot]

Using '>=' version constraint for rails_admin allows automatic upgrades to any future major version. Consider using '~> 3.0' to prevent breaking changes from potential 4.x releases.

Suggested change

	gem 'rails_admin', '>= 3.0.0'
	gem 'rails_admin', '~> 3.0'

[Copilot]

Using '>=' version constraint for sequenced allows automatic upgrades to any future major version. Consider using '~> 3.2' to prevent breaking changes from potential 4.x releases.

Suggested change

	gem 'sequenced', '>= 3.2.0'
	gem 'sequenced', '~> 3.2'