[Snyk] Security upgrade jsbundling-rails from 1.1.2 to 1.2.0

[JJediny]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `rubygems` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • Gemfile
  • Gemfile.lock

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	616/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 5.9	Web Cache Poisoning SNYK-RUBY-RACK-1061917	No	Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Check the changes in this PR to ensure they won't cause issues with your project.

---

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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

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

[aduth]

This mentions JSBundling as the upgrade, but the issue listed is the same as in #7193. I don't see any security-related changes in the recent releases of JSBundling. We can upgrade, but (a) I'd rather avoid touching the "Ruby" version in Gemfile.lock if possible, and (b) we should upgrade to the latest version which is 1.2.1, not 1.2.0.