Skip to content

fix(deps): update backstage monorepo - #49

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/backstage-monorepo
Open

fix(deps): update backstage monorepo#49
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/backstage-monorepo

Conversation

@renovate

@renovate renovate Bot commented Feb 6, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@backstage/cli (source) ^0.26.0 → ^0.36.0 age confidence
@backstage/core-app-api (source) 1.14.2 → 1.20.3 age confidence
@backstage/core-components (source) ^0.14.3 → ^0.18.0 age confidence
@backstage/core-plugin-api (source) 1.9.3 → 1.12.8 age confidence
@backstage/dev-utils (source) 1.0.37 → 1.1.25 age confidence
@backstage/plugin-catalog-react (source) 1.12.3 → 1.21.6 age confidence
@backstage/test-utils (source) 1.5.10 → 1.7.20 age confidence
@backstage/theme (source) ^0.5.2 → ^0.7.0 age confidence

Release Notes

backstage/backstage (@​backstage/cli)

v0.36.4

Compare Source

Patch Changes

v0.36.3

Compare Source

Patch Changes

v0.36.2

Compare Source

Patch Changes

v0.36.1

Compare Source

Patch Changes

v0.36.0

Compare Source

Minor Changes

  • d0f4cd2: Added new auth command group for authenticating the CLI with Backstage instances using OAuth 2.0 with a pre-registered client metadata document. Commands include login, logout, list, show, print-token, and select for managing multiple authenticated instances.

  • d806b0c: The CLI now automatically discovers CLI modules from the project root's dependencies and devDependencies. Any installed package with the cli-module Backstage role will be loaded automatically without needing to be hardcoded in the CLI itself.

    If no CLI modules are found in the project dependencies, the CLI falls back to the built-in set of modules and prints a deprecation warning. This fallback will be removed in a future release. To prepare for this, add @backstage/cli-defaults as a devDependency in your root package.json:

    {
  "devDependencies": {
    "@backstage/cli-defaults": "backstage:^"
  }
}

    If you are not using the Backstage Yarn plugin, run the following instead:

    yarn workspace root add --dev @backstage/cli-defaults

    For fine-grained control you can instead install individual CLI modules:

    {
  "devDependencies": {
    "@backstage/cli-module-auth": "backstage:^",
    "@backstage/cli-module-build": "backstage:^",
    "@backstage/cli-module-config": "backstage:^",
    "@backstage/cli-module-github": "backstage:^",
    "@backstage/cli-module-info": "backstage:^",
    "@backstage/cli-module-lint": "backstage:^",
    "@backstage/cli-module-maintenance": "backstage:^",
    "@backstage/cli-module-migrate": "backstage:^",
    "@backstage/cli-module-new": "backstage:^",
    "@backstage/cli-module-test-jest": "backstage:^",
    "@backstage/cli-module-translations": "backstage:^"
  }
}

  • 08d9770: BREAKING: The CLI templates for frontend plugins have been renamed:

    • new-frontend-plugin → frontend-plugin
    • new-frontend-plugin-module → frontend-plugin-module
    • frontend-plugin (legacy) → legacy-frontend-plugin

    To smooth out this breaking change, the CLI now auto-detects which frontend system your app uses based on the dependencies in packages/app/package.json. When using the default templates (no explicit templates configuration):

    • Apps using @backstage/frontend-defaults will see the new frontend system templates (frontend-plugin, frontend-plugin-module)
    • Apps using @backstage/app-defaults will see the legacy template (displayed as frontend-plugin)

    This means existing projects that haven't migrated to the new frontend system will continue to create legacy plugins by default, while new projects will get the new frontend system templates. If you have explicit template configuration in your package.json, it will be used as-is without any auto-detection.

  • b36a60d: BREAKING: The migrate package-exports command has been removed. Use repo fix instead.

Patch Changes

  • edf2b77: Added a new cli-module template for creating CLI module packages.

  • 246877a: Updated dependency bfj to ^9.0.2.

  • 0d2d0f2: Internal refactor of CLI modularization, moving individual commands to be implemented with cleye.

  • a4e5902: Internal refactor of the CLI command registration

  • bba2e49: Internal refactor to use new concurrency utilities from @backstage/cli-node.

  • 2fcba39: Internal refactor to move shared utilities into their consuming modules, reducing cross-module dependencies.

  • c85ac86: Internal refactor to split loadCliConfig into separate implementations for the build and config CLI modules, removing a cross-module dependency.

  • 94a885a: Added support for the new cli-module package role in the build system, ESLint configuration, Jest configuration, and maintenance commands.

  • fd50cb3: Added translations export and translations import commands for managing translation files.

    The translations export command discovers all TranslationRef definitions across frontend plugin dependencies and exports their default messages as JSON files. The translations import command generates TranslationResource wiring code from translated JSON files, ready to be plugged into the app.

    Both commands support a --pattern option for controlling the message file layout, for example --pattern '{lang}/{id}.json' for language-based directory grouping.

  • 0be3eab: Migrated CLI plugin modules to use createCliModule from @backstage/cli-node.

  • 61cb976: Migrated internal versioning utilities to use @backstage/cli-node instead of a local implementation.

  • 6738cf0: build(deps): bump minimatch from 9.0.5 to 10.2.1

  • ff4a45a: Migrated remaining CLI command handlers from commander to cleye for argument parsing. Several camelCase CLI flags have been deprecated in favor of their kebab-case equivalents (e.g. --successCache → --success-cache). The old camelCase forms still work but will now log a deprecation warning. Please update any scripts or CI configurations to use the kebab-case versions.

  • 70fc178: Migrated from deprecated findPaths to targetPaths and findOwnPaths from @backstage/cli-common.

  • 825c81d: Internal refactor of CLI command modules.

  • ea90ab0: The built-in yarn new templates have been moved to @backstage/cli-module-new. Existing references to @backstage/cli/templates/* in your root package.json will continue to work through a backwards compatibility rewrite in the new command.

  • ebeb0d4: Updated the new frontend plugin template to use @backstage/frontend-dev-utils in its dev/ entry point instead of wiring createApp manually. Generated plugins now get the same dev app helper setup as the built-in examples.

  • 971cc94: The new command now prompts for the plugin package name when creating plugin modules, in order to properly populate the package.json file.

  • de62a9d: Upgraded commander dependency from ^12.0.0 to ^14.0.3 across all CLI packages.

  • 092b41f: Updated dependency webpack to ~5.105.0.

  • 4a75544: Updated dependency react-refresh to ^0.18.0.

  • a9d23c4: Properly support package.json workspaces field

  • Updated dependencies

v0.35.4

Compare Source

Patch Changes

  • cfd8103: Updated catalog provider module template to use stable catalog extension points from @backstage/plugin-catalog-node instead of alpha exports.

  • 20131c5: Added support for CSS exports in package builds. When a package declares a CSS file in its exports field (e.g., "./styles.css": "./src/styles.css"), the CLI will automatically bundle it during backstage-cli package build, resolving any @import statements. The export path is rewritten from src/ to dist/ at publish time.

    Fixed backstage-cli repo fix to not add typesVersions entries for non-script exports like CSS files.

  • 7455dae: Use node prefix on native imports

  • 6ce4a13: Removed /alpha from scaffolderActionsExtensionPoint import

  • fdbd404: Removed the EXPERIMENTAL_MODULE_FEDERATION environment variable flag, making module federation host support always available during package start. The host shared dependencies are now managed through @backstage/module-federation-common and injected as a versioned runtime script at build time.

  • fdbd404: Updated @module-federation/enhanced, @module-federation/runtime, and @module-federation/sdk dependencies from ^0.9.0 to ^0.21.6.

  • 4fc7bf0: Bump to tar v7

  • 5e3ef57: Added support for the new peerModules metadata field in package.json. This field allows plugin packages to declare modules that should be installed alongside them for cross-plugin integrations. The field is validated by backstage-cli repo fix --publish.

  • 122d39c: Completely removed support for the deprecated app.experimental.packages configuration. Replace existing usage directly with app.packages.

  • 73351c2: Updated dependency webpack to ~5.104.0.

  • 69d880e: Bump to latest zod to ensure it has the latest features

  • Updated dependencies

v0.35.3

Compare Source

Patch Changes

v0.35.2

Compare Source

Patch Changes
  • 320c6a9: Bump @swc/core to support ES2023 and ES2024
  • c0d7bf6: Added --include and --format options to backstage-cli info command for including additional packages via glob patterns and outputting as JSON or Text.
  • f6a5d2f: Fixed CSS module class name collisions when running multiple versions of packages simultaneously by using content-based hashing for class name generation.
  • 140cbc2: Added @backstage/backend-test-utils to backend package templates.
  • 4eeba9e: Upgrade zod-validation-error to version 4
  • 9ee5996: Bump minimum required @swc/core to avoid transpilation bug
  • Updated dependencies

v0.35.1

Compare Source

Hey, I just made a Pull Request!

I created a module for Rails and one action to use rails new in the scaffolder

Addesd to the plugin list:
image

✔️ Checklist
  • A changeset describing the change and affected packages. (more info)
  • Added or updated documentation
  • Tests for new functionality and regression tests for bug fixes
  • Screenshots attached (for UI changes)
  • All your commits have a Signed-off-by line in the message. (more info)

v0.35.0

Compare Source

Minor Changes

  • f6f22a9: Provide --no-node-snapshot by default when running the package start or package test. You can disable this behavior by providing NODE_OPTIONS='--node-snapshot'.

  • f8dff94: Switched the default module resolution to bundler and the module setting to ES2020.

    You may need to bump some dependencies as part of this change and fix imports in code. The most common source of this is that type checking will now consider the exports field in package.json when resolving imports. This in turn can break older versions of packages that had incompatible exports fields. Generally these issues will have already been fixed in the upstream packages.

    You might be tempted to use --skipLibCheck to hide issues due to this change, but it will weaken the type safety of your project. If you run into a large number of issues and want to keep the old behavior, you can reset the moduleResolution and module settings your own tsconfig.json file to node and ESNext respectively. But keep in mind that the node option will be removed in future versions of TypeScript.

    A future version of Backstage will make these new settings mandatory, as we move to rely on the exports field for type resolution in packages, rather than the typesVersions field.

  • cd0b8a1: BREAKING: jest is now a peer dependency. If you run tests using Backstage CLI, you must add Jest and its environment dependencies as devDependencies in your project.

    You can choose to install either Jest 29 or Jest 30. The built-in Jest version before this change was Jest 29, however, we recommend that you switch to Jest 30. Upgrading will solve the Could not parse CSS stylesheet errors, allow you to use MSW v2 in web packages, and ensure that you remain compatible with future versions of the Backstage CLI. Support for Jest 29 is temporary, with the purpose of allowing you to upgrade at your own pace, but it will eventually be removed.

    • Jest 29: Install jest@^29 and jest-environment-jsdom@^29. No migration needed, but you may see Could not parse CSS stylesheet warnings/errors when testing components from @backstage/ui or other packages using CSS @layer declarations.
    • Jest 30: Install jest@^30, @jest/environment-jsdom-abstract@^30, and jsdom@^27. Fixes the stylesheet parsing warnings/errors, but requires migration steps.

    See the Jest 30 migration guide for detailed migration instructions.

Patch Changes

  • de96a60: chore(deps): bump express from 4.21.2 to 4.22.0

  • e7db290: Add missing peer/dev dependencies to the frontend plugin template.

    react-dom was not declared as a peer dependency, causing module resolution
    errors when generating plugins outside a Backstage monorepo. This adds
    react-dom to peerDependencies (for consuming apps) and devDependencies
    (for local development). react-router-dom is also added to peerDependencies (for consuming apps) and devDependencies
    to support routing during plugin development.

    Fixes:

    • Module not found: Can't resolve 'react-dom'
    • Module not found: Can't resolve 'react-router-dom'

  • 1226647: Updated dependency esbuild to ^0.27.0.

  • f89a074: Updated dependency @pmmmwh/react-refresh-webpack-plugin to ^0.6.0.

  • 2b81751: Updated dependency webpack to ~5.103.0.

  • fafd9e1: Fixed internal usage of yargs.

  • c8c2329: Add proxy configuration from env-vars to create-app tasks

  • 2bae83a: Switched compilation target to ES2022 in order to match the new set of supported Node.js versions, which are 22 and 24.

    The TypeScript compilation target has been set to ES2022, because setting it to a higher target will break projects on older TypeScript versions. If you use a newer TypeScript version in your own project, you can bump compilerOptions.target to ES2023 or ES2024 in your own tsconfig.json file.

  • 7fbac5c: Updated to use new utilities from @backstage/cli-common.

  • 2bae83a: Bumped dev dependencies @types/node

  • Updated dependencies

v0.34.6

Compare Source

Patch Changes

v0.34.5

Compare Source

Patch Changes
  • fc7cbfc: The templates executed with the yarn new command now supports templating filenames.
  • da19cb5: Fix inconsistent behavior in the new command for the @internal scope: it now consistently defaults to the backstage-plugin- infix whether the --scope option is not set or it's set to internal.
  • fc7cbfc: Added a template for the yarn new command to create an catalog entity provider. To add this template to an explicit list in the root package.json, use @backstage/cli/templates/catalog-provider-module.
  • b2bef92: Convert all enums to erasable-syntax compliant patterns
  • 279279c: Fixes an issue where using the backstage-cli new --scope command with a scope that already includes the @ symbol (e.g., @backstage-community) would result in a double @@ prefix in the generated package name, causing invalid package.json files.
  • 05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript's erasableSyntaxOnly setting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.
  • Updated dependencies

v0.34.4

Compare Source

Patch Changes

  • f2cf564: Removed the script transform cache from the default Jest configuration. The script cache provided a moderate performance boost, but it is incompatible with Jest 30.

  • 33faad2: Allow using custom manifest location in the yarn plugin and version bump.

    The Backstage yarn plugin and version bump allows two new environment variables to configure custom manifest location:

    • BACKSTAGE_VERSIONS_BASE_URL: The base URL for fetching the Backstage version
      manifest. Defaults to https://versions.backstage.io/v1/releases/VERSION/manifest.json.
      Useful for running the plugin in environment without direct access to the internet,
      for example by using a mirror of the versions API or a proxy.
      Note that the environment variable is just the host name, and the path is appended by
      the plugin. If you are using the yarn plugin, bump version command will also try
      to fetch the new version of the yarn plugin from the same base URL (defaults to
      https://versions.backstage.io/v1/releases/RELEASE/yarn-plugin)
    • BACKSTAGE_MANIFEST_FILE: Path to a local manifest file. If set, the plugin
      will not attempt to fetch the manifest from the network. Useful for running
      the plugin in environment without internet access and without mirror of the
      versions API.

  • 6ebc1ea: Fixed module federation config by only setting import: false on shared libraries for remote.

  • ab96bb7: Added a new --entrypoint option to the package start command, which allows you to specify a custom entry directory/file for development applications. This is particularly useful when maintaining separate dev apps for different versions of your plugin (e.g., stable and alpha).

    Example usage:

    Consider the following plugin dev folder structure:

    dev/
  index.tsx
  alpha/
    index.ts
    • The default yarn package start command uses the dev/ folder as the entry point and executes dev/index.tsx file;
    • Running yarn package start --entrypoint dev/alpha will instead use dev/alpha/ as the entry point and execute dev/alpha/index.ts file.

  • 024645e: Remove unused @​octokit modules from cli package

  • d14ef24: Added automatic detection and support for the Backstage Yarn plugin when generating new packages with yarn new. When the plugin is installed, new packages will automatically use backstage:^ ranges for @backstage/* dependencies.

  • Updated dependencies

v0.34.3

Compare Source

v0.34.2

Compare Source

Patch Changes

  • e6f45dc: Updated the WebPack configuration to use contenthash. This fixes an issue were builds would sometimes generate output files with the same name but different content across builds, leading to breakages when loading the frontend app.

  • fffd434: Disallow import fallback of critical shared dependencies in module federation.

  • 080f252: Fixed the new-frontend-plugin template that was incorrectly passing id instead of pluginId to createFrontendPlugin and unnecessarily importing React.

  • e0db9b8: Modify the backstage.json also for custom patterns if it extends the default pattern.

    Examples:

    • @backstage/* (default pattern)
    • @{backstage,backstage-community}/*
    • @{extra1,backstage,extra2}/*

  • 275bda8: Fixed an issue that could cause conflicts of detected modules in workspaces with multiple apps.

  • e1adce4: Updated the backend plugin template to use a new pattern for the TodoListService that reduces boilerplate.

  • Updated dependencies

v0.34.1

Compare Source

Patch Changes

v0.34.0

Compare Source

Minor Changes

  • 38b4243: Added plugin and module templates for the new frontend system. These templates are not included by default, but can be included by adding @backstage/cli/templates/new-frontend-plugin and @backstage/cli/templates/new-frontend-plugin-module as custom templates.

  • 923ceb2: BREAKING: The new app build based on Rspack is now the default, and the EXPERIMENTAL_RSPACK flag has been removed. To revert to the old behavior, set the LEGACY_WEBPACK_BUILD environment flag and install the following optional dependencies:

    {
  "dependencies": {
    "@module-federation/enhanced": "^0.9.0",
    "@pmmmwh/react-refresh-webpack-plugin": "^0.5.7",
    "esbuild-loader": "^4.0.0",
    "eslint-webpack-plugin": "^4.2.0",
    "fork-ts-checker-webpack-plugin": "^9.0.0",
    "mini-css-extract-plugin": "^2.4.2",
    "terser-webpack-plugin": "^5.1.3",
    "webpack": "^5.96.0",
    "webpack-dev-server": "^5.0.0"
  }
}

    If you do encounter a blocking issue that forces you to use the old WebPack build, please open an issue explaining the problem. The WebPack build will be removed in a future release.

  • eda80c7: BREAKING: Removed support for .icon.svg imports, which have been deprecated since the 1.19 release.

Patch Changes
  • 2b8082a: Internal refactor of error handling
  • 8b1bf6e: Deprecated new frontend system config setting app.experimental.packages to just app.packages. The old config will continue working for the time being, but may be removed in a future release.
  • ead626f: The Node.js transform in @backstage/cli/config/nodeTransformHooks.mjs now supports the built-in type stripping in Node.js, which is enabled by default from v22.18.0.
  • a6af768: Allow js files to be processed by the nodeTransform loader
  • Updated dependencies

v0.33.1

Compare Source

Patch Changes

v0.33.0

Compare Source

Minor Changes
  • eef0e83: Internal update to promote the modular CLI entrypoint to stable.
Patch Changes

v0.32.1

Compare Source

Patch Changes

v0.32.0

Compare Source

Minor Changes
Patch Changes

  • 4ea76f7: Bump @​module-federation/enhanced ^0.9.0 to fix GHSA-593f-38f6-jp5m

  • 87a5cb4: Fixed an issue causing the repo lint command to fail when the --max-warnings option was used.

  • 6969f79: Avoid trailing /* when automatically adding imports for package with multiple entry points.

  • 98b7131: Update the to do plugin template to stop using the deprecated catalog alpha service reference.
    If you start seeing the should create TODO item with catalog information test failing, you have two options to fix this:
    Update the test to mock the legacy alpha catalog service, or migrate the TODO plugin backend to use the new catalog service reference.
    We recommend the second option, see this pull request for an example of how to do the migration.

  • d5c4fed: make certificate strings optional for Dev environments

  • d83f3f4: Resolved a problem where the start command did not correctly handle multiple --require flags, ensuring all specified modules are now properly loaded.

  • d2091c6: Added a new repo start command to replace the existing pattern of using yarn dev scripts. The repo start command runs the app and/or backend package in the repo by default, but will also fall back to running other individual frontend or backend packages or even plugin dev entry points if the can be uniquely selected.

    The goal of this change is to reduce the number of different necessary scripts and align on yarn start being the only command needed for local development, similar to how repo test handles testing in the repo. It also opens up for more powerful options, like the --plugin <pluginId> flag that runs the dev entry point of the selected plugin.

    The new script is installed as follows, replacing the existing yarn start script:

    {
  "scripts": {
    "start": "backstage-cli repo start"
  }
}

    In order to help users migrate in existing projects, it is recommended to add the following scripts to the root package.json:

    {
  "scripts": {
    "dev": "echo \"Use 'yarn start' instead\"",
    "start-backend": "echo \"Use 'yarn start backend' instead\""
  }
}

    For more information, run yarn start --help once the new command is installed.

  • 918c883: Included a reference to the JSX transform guide in the warning about using the default React import.

  • Updated dependencies

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Feb 6, 2025
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch from e66f6d6 to 8b4447e Compare February 18, 2025 17:40
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch from 8b4447e to 6bbd769 Compare March 18, 2025 14:56
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch from 6bbd769 to 180e34d Compare April 3, 2025 16:07
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch from 180e34d to 34a8476 Compare April 15, 2025 20:23
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch from 34a8476 to 090e9ea Compare May 20, 2025 15:04
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch from 090e9ea to 50ee23a Compare May 29, 2025 20:14
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch from 50ee23a to fa9f935 Compare June 17, 2025 17:44
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch from fa9f935 to b5c3a9e Compare July 15, 2025 19:07
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch 2 times, most recently from d835449 to c934d36 Compare August 20, 2025 19:26
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch 2 times, most recently from 0b942dc to 5caa7f7 Compare September 19, 2025 22:41
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch 3 times, most recently from f7d4b0b to 56fe49e Compare October 15, 2025 19:31
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch from 56fe49e to a704ffb Compare November 18, 2025 23:06
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch 2 times, most recently from eaf906b to 2adb98e Compare December 16, 2025 20:08
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch from 2adb98e to 751763d Compare January 20, 2026 22:37
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch from 751763d to 9437699 Compare January 28, 2026 12:01
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch from 9437699 to 2a95cb2 Compare February 18, 2026 00:41
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch from 2a95cb2 to d195e38 Compare March 18, 2026 02:13
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch 2 times, most recently from a8a4bd8 to 0df69b8 Compare April 16, 2026 13:33
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch from 0df69b8 to 7ff1666 Compare May 19, 2026 23:06
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch from 7ff1666 to 350ea9c Compare June 16, 2026 21:12
@renovate
renovate Bot force-pushed the renovate/backstage-monorepo branch from 350ea9c to c577f60 Compare July 14, 2026 12:48
cursor[bot]
cursor Bot approved these changes Jul 14, 2026
View reviewed changes

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Risk: medium. Approved: Cursor Bugbot and Cursor Security Agent checks were not present on this PR, and there are no automated findings requiring human review. This is a bounded Backstage monorepo dependency bump (package.json/yarn.lock only).

Open in Web View Automation 

Sent by Cursor Approval Agent: Pull Request Router and Approver

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@cursor cursor[bot] cursor[bot] approved these changes

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants