[Snyk] Fix for 1 vulnerabilities

[snyk-io]

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

Snyk changed the following file(s):

• plugins/rollbar-backend/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	Score
	Regular Expression Denial of Service (ReDoS) SNYK-JS-BABELRUNTIME-10044504	738

---

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:

🦉 Regular Expression Denial of Service (ReDoS)

Summary by Sourcery

Update dependencies to fix a security vulnerability in the Rollbar backend plugin

Bug Fixes:

• Resolve a Regular Expression Denial of Service (ReDoS) vulnerability in @babel/runtime

Enhancements:

• Update @backstage/backend-common from workspace version to 0.24.1
• Update @backstage/config from workspace version to 0.1.1

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[restack-app]

No applications have been configured for previews targeting branch: master. To do so go to restack console and configure your applications for previews.

[sourcery-ai]

Reviewer's Guide

This PR, automatically generated by Snyk, addresses a reported vulnerability by updating the versions of @backstage/backend-common and @backstage/config dependencies to specific, fixed versions within the plugins/rollbar-backend/package.json file. Please note that the yarn.lock file was not automatically updated and will require manual intervention before merging.

Sequence Diagram: Required Manual yarn.lock Update Process

sequenceDiagram
    title: Required Manual yarn.lock Update Process
    participant Snyk as Snyk Automation
    actor Developer
    participant Repository
    participant LocalEnv as Local Dev Environment

    Snyk->>Repository: Creates PR with package.json changes
    note over Snyk,Repository: yarn.lock update failed during PR creation as per PR warning

    Developer->>Repository: Reviews PR (notices yarn.lock issue)
    Developer->>LocalEnv: Pulls PR changes (e.g., git pull)
    Developer->>LocalEnv: Runs package manager command to update lockfile (e.g., yarn install)
    LocalEnv-->>Developer: yarn.lock is updated locally
    Developer->>Repository: Commits updated yarn.lock to PR branch (e.g., git commit, git push)
    Developer->>Repository: Merges PR (now including correct yarn.lock)

Loading

File-Level Changes

Change	Details	Files
Updated dependency versions to fixed versions to resolve a Snyk-reported vulnerability.	Changed @backstage/backend-common from workspace:^ to 0.24.1. Changed @backstage/config from workspace:^ to 0.1.1.	plugins/rollbar-backend/package.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[graphite-app]

The version 0.1.1 for @backstage/config appears to be significantly outdated compared to the 0.24.1 version specified for @backstage/backend-common. These packages are typically versioned to be compatible with each other, and using mismatched versions may lead to runtime errors or unexpected behavior.

Consider updating @backstage/config to a version that aligns with @backstage/backend-common 0.24.1 to ensure compatibility. The Backstage packages generally follow a coordinated versioning strategy where compatible packages are released together.

Suggested change

	"@backstage/config": "0.1.1",
	+ "@backstage/config": "0.24.1",

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

[snyk-io]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[github-actions]

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!