[Snyk] Fix for 1 vulnerabilities

[Eric-Guo]

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

Snyk changed the following file(s):

• package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning

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

Vulnerabilities that will be fixed with an upgrade:

	Issue
	Uncontrolled Recursion SNYK-JS-POSTCSSSELECTORPARSER-16873882

---

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:

🦉 Uncontrolled Recursion

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: faa39a7590

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Regenerate the pnpm lockfile for CoreUI upgrades

These manifest changes are not reflected in pnpm-lock.yaml: the lockfile importer still pins @coreui/chartjs to specifier ^3.1.2/version 3.1.2 and @coreui/coreui to specifier/version 4.2.6. I checked the CI install steps in .github/workflows/rubyonrails.yml:54 and .gitlab-ci.yml:30, and both run pnpm install --frozen-lockfile; pnpm documents that this mode fails when the lockfile is out of sync with the manifest, so this commit will fail dependency installation before tests/assets run. Please rerun pnpm install and commit the regenerated lockfile for these two upgrades.

Useful? React with 👍 / 👎.

[Copilot]

Pull request overview

This Snyk-driven dependency update attempts to remediate a reported JS vulnerability by bumping several frontend dependencies (notably CoreUI and Babel/Webpack), and also includes a couple of Ruby gem patch updates.

Changes:

• Bumps Babel toolchain and Webpack versions.
• Upgrades CoreUI packages to new major versions in package.json.
• Updates Gemfile.lock patch versions for jbuilder and puma.

Reviewed changes

Copilot reviewed 1 out of 3 changed files in this pull request and generated 2 comments.

File	Description
package.json	Updates JS dependency versions (incl. major CoreUI upgrades) and Webpack patch bump.
pnpm-lock.yaml	Updates lockfile resolutions for Babel/Webpack, but currently does not reflect the CoreUI upgrades in package.json.
Gemfile.lock	Patch bumps jbuilder and puma, expanding scope beyond the PR description.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.