Skip to content

Comments

chore(deps): update dependency @backstage/cli to ^0.35.0#228

Open
red-hat-konflux[bot] wants to merge 1 commit intomainfrom
konflux/mintmaker/main/backstage-monorepo
Open

chore(deps): update dependency @backstage/cli to ^0.35.0#228
red-hat-konflux[bot] wants to merge 1 commit intomainfrom
konflux/mintmaker/main/backstage-monorepo

Conversation

@red-hat-konflux
Copy link
Contributor

@red-hat-konflux red-hat-konflux bot commented Jan 16, 2026

This PR contains the following updates:

Package Change Age Confidence
@backstage/cli (source) ^0.34.4 -> ^0.35.0 age confidence
@backstage/cli (source) ^0.34.1 -> ^0.35.0 age confidence
@backstage/cli (source) ^0.34.0 -> ^0.35.0 age confidence
@backstage/cli (source) ^0.34.5 -> ^0.35.0 age confidence

Release Notes

backstage/backstage (@​backstage/cli)

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.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

Configuration

📅 Schedule: 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.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


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

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

@red-hat-konflux red-hat-konflux bot requested a review from a team as a code owner January 16, 2026 18:14
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/main/backstage-monorepo branch 7 times, most recently from 0993f0f to cc906de Compare January 18, 2026 01:39
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/main/backstage-monorepo branch from cc906de to 37474af Compare February 10, 2026 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants