chore(deps): update dependency @backstage/cli to ^0.35.0#228
Open
red-hat-konflux[bot] wants to merge 1 commit intomainfrom
Open
chore(deps): update dependency @backstage/cli to ^0.35.0#228red-hat-konflux[bot] wants to merge 1 commit intomainfrom
red-hat-konflux[bot] wants to merge 1 commit intomainfrom
Conversation
0993f0f to
cc906de
Compare
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
cc906de to
37474af
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^0.34.4->^0.35.0^0.34.1->^0.35.0^0.34.0->^0.35.0^0.34.5->^0.35.0Release Notes
backstage/backstage (@backstage/cli)
v0.35.4Compare Source
Patch Changes
cfd8103: Updated catalog provider module template to use stable catalog extension points from@backstage/plugin-catalog-nodeinstead of alpha exports.20131c5: Added support for CSS exports in package builds. When a package declares a CSS file in itsexportsfield (e.g.,"./styles.css": "./src/styles.css"), the CLI will automatically bundle it duringbackstage-cli package build, resolving any@importstatements. The export path is rewritten fromsrc/todist/at publish time.Fixed
backstage-cli repo fixto not addtypesVersionsentries for non-script exports like CSS files.7455dae: Use node prefix on native imports6ce4a13: Removed/alphafromscaffolderActionsExtensionPointimportfdbd404: Removed theEXPERIMENTAL_MODULE_FEDERATIONenvironment variable flag, making module federation host support always available duringpackage start. The host shared dependencies are now managed through@backstage/module-federation-commonand injected as a versioned runtime script at build time.fdbd404: Updated@module-federation/enhanced,@module-federation/runtime, and@module-federation/sdkdependencies from^0.9.0to^0.21.6.4fc7bf0: Bump to tar v75e3ef57: Added support for the newpeerModulesmetadata field inpackage.json. This field allows plugin packages to declare modules that should be installed alongside them for cross-plugin integrations. The field is validated bybackstage-cli repo fix --publish.122d39c: Completely removed support for the deprecatedapp.experimental.packagesconfiguration. Replace existing usage directly withapp.packages.73351c2: Updated dependencywebpackto~5.104.0.69d880e: Bump to latest zod to ensure it has the latest featuresUpdated dependencies
v0.35.3Compare Source
Patch Changes
cfd8103: Updated catalog provider module template to use stable catalog extension points from@backstage/plugin-catalog-nodeinstead of alpha exports.7455dae: Use node prefix on native imports4fc7bf0: Bump to tar v7122d39c: Completely removed support for the deprecatedapp.experimental.packagesconfiguration. Replace existing usage directly withapp.packages.69d880e: Bump to latest zod to ensure it has the latest featuresv0.35.2Compare Source
Patch Changes
320c6a9: Bump@swc/coreto supportES2023andES2024c0d7bf6: Added--includeand--formatoptions tobackstage-cli infocommand 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-utilsto backend package templates.4eeba9e: Upgradezod-validation-errorto version 49ee5996: Bump minimum required@swc/coreto avoid transpilation bugv0.35.1Compare Source
Hey, I just made a Pull Request!
I created a module for Rails and one action to use
rails newin the scaffolderAddesd to the plugin list:

✔️ Checklist
Signed-off-byline in the message. (more info)v0.35.0Compare Source
Minor Changes
f6f22a9: Provide--no-node-snapshotby default when running thepackage startorpackage test. You can disable this behavior by providingNODE_OPTIONS='--node-snapshot'.f8dff94: Switched the default module resolution tobundlerand themodulesetting toES2020.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
exportsfield inpackage.jsonwhen resolving imports. This in turn can break older versions of packages that had incompatibleexportsfields. Generally these issues will have already been fixed in the upstream packages.You might be tempted to use
--skipLibCheckto 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 themoduleResolutionandmodulesettings your owntsconfig.jsonfile tonodeandESNextrespectively. But keep in mind that thenodeoption 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
exportsfield for type resolution in packages, rather than thetypesVersionsfield.cd0b8a1: BREAKING:jestis now a peer dependency. If you run tests using Backstage CLI, you must add Jest and its environment dependencies asdevDependenciesin 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 stylesheeterrors, 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@^29andjest-environment-jsdom@^29. No migration needed, but you may seeCould not parse CSS stylesheetwarnings/errors when testing components from@backstage/uior other packages using CSS@layerdeclarations.jest@^30,@jest/environment-jsdom-abstract@^30, andjsdom@^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): bumpexpressfrom 4.21.2 to 4.22.0e7db290: Add missing peer/dev dependencies to the frontend plugin template.react-domwas not declared as a peer dependency, causing module resolutionerrors when generating plugins outside a Backstage monorepo. This adds
react-domtopeerDependencies(for consuming apps) anddevDependencies(for local development).
react-router-domis also added topeerDependencies(for consuming apps) anddevDependenciesto support routing during plugin development.
Fixes:
1226647: Updated dependencyesbuildto^0.27.0.f89a074: Updated dependency@pmmmwh/react-refresh-webpack-pluginto^0.6.0.2b81751: Updated dependencywebpackto~5.103.0.fafd9e1: Fixed internal usage ofyargs.c8c2329: Add proxy configuration from env-vars to create-app tasks2bae83a: 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.targetto ES2023 or ES2024 in your owntsconfig.jsonfile.7fbac5c: Updated to use new utilities from@backstage/cli-common.2bae83a: Bumped dev dependencies@types/nodeUpdated dependencies
v0.34.5Compare Source
Patch Changes
fc7cbfc: The templates executed with theyarn newcommand now supports templating filenames.da19cb5: Fix inconsistent behavior in thenewcommand for the@internalscope: it now consistently defaults to thebackstage-plugin-infix whether the--scopeoption is not set or it's set tointernal.fc7cbfc: Added a template for theyarn newcommand to create an catalog entity provider. To add this template to an explicit list in the rootpackage.json, use@backstage/cli/templates/catalog-provider-module.b2bef92: Convert all enums to erasable-syntax compliant patterns279279c: Fixes an issue where using thebackstage-cli new --scopecommand with a scope that already includes the@symbol (e.g.,@backstage-community) would result in a double@@​prefix in the generated package name, causing invalidpackage.jsonfiles.05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript'serasableSyntaxOnlysetting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.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.
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.