Skip to content

fix(deps): update backstage monorepo#49

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

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

Conversation

@renovate
Copy link
Copy Markdown
Contributor

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

ℹ️ 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.34.0 age confidence
@backstage/core-app-api (source) 1.14.2 → 1.20.0 age confidence
@backstage/core-components (source) ^0.14.3 → ^0.18.0 age confidence
@backstage/core-plugin-api (source) 1.9.3 → 1.12.5 age confidence
@backstage/dev-utils (source) 1.0.37 → 1.1.22 age confidence
@backstage/plugin-catalog-react (source) 1.12.3 → 1.21.6 age confidence
@backstage/test-utils (source) 1.5.10 → 1.7.17 age confidence
@backstage/theme (source) ^0.5.2 → ^0.7.0 age confidence

Release Notes

backstage/backstage (@​backstage/cli)

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

v0.31.1

Compare Source

v0.31.0

Compare Source

Minor Changes

  • 5b70679: BREAKING: ESLint warnings no longer trigger system exit codes like errors do.

    Set the max number of warnings to -1 during linting to enable the gradual adoption of new ESLint rules. To restore the previous behavior, include the --max-warnings 0 flag in the backstage-cli <repo|package> lint command.

Patch Changes

v0.30.0

Compare Source

Minor Changes

  • cb76663: BREAKING: Add support for native ESM in Node.js code. This changes the behavior of dynamic import expressions in Node.js code. Typically this can be fixed by replacing import(...) with require(...), with an as typeof import(...) cast if needed for types. This is because dynamic imports will no longer be transformed to require(...) calls, but instead be left as-is. This in turn allows you to load ESM modules from CommonJS code using import(...).

    This change adds support for the following in Node.js packages, across type checking, package builds, runtime transforms and Jest tests:

    • Dynamic imports that load ESM modules from CommonJS code.
    • Both .mjs and .mts files as explicit ESM files, as well as .cjs and .cts as explicit CommonJS files.
    • Support for the "type": "module" field in package.json to indicate that the package is an ESM package.

    There are a few caveats to be aware of:

    • To enable support for native ESM in tests, you need to run the tests with the --experimental-vm-modules flag enabled, typically via NODE_OPTIONS='--experimental-vm-modules'.
    • Declaring a package as "type": "module" in package.json is supported, but in tests it will cause all local transitive dependencies to also be treated as ESM, regardless of whether they declare "type": "module" or not.
    • Node.js has an ESM interoperability layer with CommonJS that allows for imports from ESM to identify named exports in CommonJS packages. This interoperability layer is only enabled when importing packages with a .cts or .cjs extension. This is because the interoperability layer is not fully compatible with the NPM ecosystem, and would break package if it was enabled for .js files.
    • Dynamic imports of CommonJS packages will vary in shape depending on the runtime, i.e. test vs local development, etc. It is therefore recommended to avoid dynamic imports of CommonJS packages and instead use require, or to use the explicit CommonJS extensions as mentioned above. If you do need to dynamically import CommonJS packages, avoid using default exports, as the shape of them vary across different environments and you would otherwise need to manually unwrap the import based on the shape of the module object.

  • b30e788: The new command is now powered by a new template system that allows you to define your own templates in a declarative way, as well as import existing templates from external sources. See the CLI templates documentation for more information.

    The following flags for the new command have been deprecated and will be removed in a future release:

    • --license=<license>: Configure the global license instead.
    • --no-private: Configure the global private instead.
    • --baseVersion=<version>: Configure the global version instead.
    • --npmRegistry=<url>: Configure the global publishRegistry instead.
    • --scope=<scope>: Configure the global namePrefix and/or namePluginInfix instead.

    As part of this change the template IDs and their options have changed. The following backwards compatibility mappings for the --select and --option flags are enabled when using the default set of templates, but they will also be removed in the future:

    • --select=plugin is mapped to --select=frontend-plugin instead.
    • --option=id=<id> is mapped to --option=pluginId=<id> instead.
Patch Changes
  • f17ef61: The versions:bump command will now reject * as a pattern.
  • 86c72c1: The packing process when running build-workspace with the --alwaysYarnPack flag now respects the BACKSTAGE_CLI_BUILD_PARALLEL environment variable, defaulting parallel work limits based on CPU availability.
  • 2167afc: Treat static file assets as always being free from side effects in package builds.
  • f54eed0: Fixed an issue where default feature type information wasn't being added to package.json/exports before publishing if exports didn't exist beforehand
  • 90a1edf: Add check to make sure that the --link option for the start command is a valid workspace.
  • 207f88f: Fixed the file path pattern of many static assets output as part of the frontend build process, where there was an extra . before the extension, leading to names like image-af7946b..png.
  • 9638f6d: Only allow pass through of .mjs in Jest transform if static ESM is supported.
  • 9d49e04: Replaced dependency node-libs-browser with node-stdlib-browser
  • 2c14147: Corrected path when trying to add dependency to respective package.json when using yarn new templates
  • f21b125: Ensure that both global-agent and undici agents are enabled when proxying is enabled.
  • Updated dependencies

v0.29.6

Compare Source

v0.29.5

Compare Source

Patch Changes

v0.29.4

Compare Source

Patch Changes
  • 2b6c1ea: If the Backstage yarn plugin is installed, it will now be automatically updated as part of versions:bump.
  • 7dcff85: Remove special-casing for @types packages when generating dependency entries
    during templating
  • 3c3a7e6: Revert css-loader@v7 bump
  • 0aff006: Bumped the version range for html-webpack-plugin to fix the htmlPluginExports.getCompilationHooks is not a function error when using experimental Rspack.
  • 583f3d4: Added @backstage/cli/config/prettier as a replacement for @spotify/prettier-config, but with the same configuration.
  • 62a9062: Updated dependency @module-federation/enhanced to ^0.8.0.
  • 5f04976: Update rollup to avoid issues with build output when running backstage-cli package build.
  • 5f04976: Fixed a bug that caused missing code in published packages.
  • a49030a: Add support for --output-file option from ESLint to package lint and repo lint commands.
  • 96331fa: Enhance the behavior of the experimental support for module federation in the backstage CLI,
    by using the package.json exports (when present) to complete the list of exposed modules.
    This allows, for example, using exported alpha definitions through module federation.
  • 5c9cc05: Use native fetch instead of node-fetch
  • dcd99d2: added experimental RSPack support for build command in the repo scope
  • Updated dependencies

v0.29.3

Compare Source

Patch Changes

v0.29.2

Compare Source

The @backstage/core package has been split into the following three packages, all published as part of this release.

Name Description
@backstage/core-app-api Core app API used by Backstage apps
@backstage/core-plugin-api Core API used by Backstage plugins and apps
@backstage/core-components Core components used by Backstage plugins and apps

The main purpose of the split is to decouple the plugin API versioning from the app. It is now possible to bring in multiple plugins that depend on different versions of the core API, without any significant overhead.

The existing @backstage/core package still works together with these new packages, meaning that there is no rush to migrate, and we do not recommend that projects are migrated just yet. In general migration will be done by simply replacing usages of @backstage/core with either @backstage/core-plugin-api, @backstage/core-app-api, or @backstage/core-components, depending on what's being imported, but more information will follow!

v0.29.1

Compare Source

Published a new @backstage/backend-test-utils package, which is a package for backend test utilities.

v0.29.0

Compare Source

Minor Changes

  • bc47b17: BREAKING: Updates ESLint config to ignore all generated source code under src/**/generated/**/*.ts.

  • 6819f8c: Added a new optimization to the repo test command that will filter out unused packages in watch mode if all provide filters are paths that point from the repo root. This significantly speeds up running individual tests from the repo root in a large workspace, for example:

    yarn test packages/app/src/App.test.tsx

  • d849865: The package packing now populates typesVersions for additional entry points rather than using additional package.json files for type resolution. This improves auto completion of separate entry points when consuming published packages.

  • bc71665: BREAKING: The LEGACY_BACKEND_START flag has been removed, along with support for src/run.ts as the development entry point.

Patch Changes

  • 4046d53: Fixed an issue where the --successCache option for the repo test and repo lint commands would be include the workspace path in generated cache keys. This previously broke caching in environments where the workspace path varies across builds.

  • 4a378d3: Fix dev server reloads of plugin discovery for new frontend system.

  • 28b60ad: The check for react-dom/client in the Jest configuration will now properly always run from the target directory.

  • 6b2888c: Fixed an issue with the --successCache flag for repo test where the tree hash for the wrong package directory would sometimes be used to generate the cache key.

  • e30b65d: Added --alwaysPack as a replacement for the now hidden --alwaysYarnPack flag for the build-workspace command.

  • be0278e: Removed circular import

  • a7f97e4: Added a new "rejectFrontendNetworkRequests" configuration flag that can be set in the "jest" field in the root package.json:

    {
  "jest": {
    "rejectFrontendNetworkRequests": true
  }
}

    This flag causes rejection of any form of network requests that are attempted to be made in frontend or common package tests. This flag can only be set in the root package.json and can not be overridden in individual package configurations.

  • 6c48ebd: Add --max-warnings -1 support to backstage-cli package lint

  • 04297a0: The --successCache option for the repo test and repo lint commands now use an additive store that keeps old entries around for a week before they are cleaned up automatically.

  • a2f0559: When using the experimental Rspack flag the app build and dev server now injects configuration via a <script type="backstage.io/config">...</script> tag in index.html rather than the process.env.APP_CONFIG definition, which will now be defined as an empty array instead.

    This requires the app to be using the config loader from the 1.31 release of Backstage. Make sure your app is using at least that version if you are upgrading to this version of the CLI.

    If you have copied the implementation of the defaultConfigLoader, make sure to update it to the new implementation. In particular the config loader needs to be able to read configuration from script tags with the type backstage.io/config.

  • b4627f2: Fixed an issue where the raw-loader for loading HTML templates was not resolved from the context of the CLI package.

  • cd1ef2b: Updated dependency vite to ^5.0.0.

  • 23f1da2: Updated dependency ts-morph to ^24.0.0.

  • b533056: Updated dependency css-loader to ^7.0.0.

  • be008c3: Updated dependency @module-federation/enhanced to ^0.7.0.

  • 6266ed3: Updated dependency del to ^8.0.0.

  • 4046d53: Fixed an issue with the repo lint command where the cache key for the --successCache option would not properly ignore files that should be ignored according to .eslintignores.

  • e19c53c: Fix for the --link flag for package start to deduplicate react-router and react-router-dom.

  • 17850a5: Update upgrade-helper link in versions:bump command to include yarnPlugin parameter when the yarn plugin is installed

  • 09ea093: Fixed an issue where .css style injection would fail for published packages.

  • 702f41d: Bumped dev dependencies @types/node

  • 5d74716: Remove unused backend-common dependency

  • b084f5a: Bump the Webpack dependency range to ^5.94.0, as our current configuration is not compatible with some older versions.

  • e565f73: Added support for .webp files in the frontend tooling.

  • 946fa34: Added a new --link <workspace-path> option for frontend builds that allow you to override module resolution to link in an external workspace at runtime.

    As part of this change the Webpack linked workspace resolution plugin for frontend builds has been removed. It was in place to support the old workspace linking where it was done by Yarn, which is no longer a working option.

  • Updated dependencies

v0.28.2

Compare Source

v0.28.1

Compare Source

v0.28.0

[Compare Source](https://redirect.github.com/backstage/backstage/com

✂ 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 from d195e38 to a8a4bd8 Compare April 15, 2026 17:11
@renovate renovate Bot force-pushed the renovate/backstage-monorepo branch from a8a4bd8 to 0df69b8 Compare April 16, 2026 13:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

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