Bump @backstage/cli from 0.10.5 to 0.14.0

Bumps @backstage/cli from 0.10.5 to 0.14.0.

Changelog

Sourced from @backstage/cli's changelog.

0.14.0

Minor Changes

1fc0cd3896: Bumped Webpack and Rollup svgr dependencies and updated the AST template for .icon.svg modules. This means that SVG icon imports are now using SVGO v2.

Patch Changes

0b74c72987: Added a new experimental and hidden backstage-cli repo lint command that can be used to lint all packages in the project, similar to lerna run lint.

532dae9c4c: The versions:bump --release next command is updated to compare the main and next release manifests and prefer the latest.

1ed305728b: Bump node-fetch to version 2.6.7 and cross-fetch to version 3.1.5

c77c5c7eb6: Added backstage.role to package.json

22862486de: The versions:bump command now filters out npm_ environment configuration when running yarn install. This has the effect of allowing it to consider local configuration files within the repository, which is the behavior that one would expect.

22862486de: The versions:bump command now also considers the root package.json when searching for updates. It has also received updates to its output, including a link the Backstage upgrade helper and silenced yarn install output.

7410e12268: Several changes were made to the new experimental package roles system. Unless you have been experimenting with using this new system, these changes have no affect on your project.

Renamed the backstage-cli migrate package-role command to backstage-cli migrate package-roles.

Updated the package role definitions by renaming app to frontend, plugin-frontend to frontend-plugin, plugin-frontend-module to frontend-plugin-module, plugin-backend to backend-plugin, and plugin-backend-module to backend-plugin-module

The backstage-cli migrate package-scripts received several tweaks to make it more accurate. It now tries to maintain existing script arguments, like --config parameters for build and start scripts.

The script command category has been renamed to package.

The backstage-cli package build command set an incorrect target directory for app and backend packages, which has been fixed.

The backend:bundle and repo build command for the backend role was previously ignoring building of bundled packages that had migrated to use package roles and the standard build script, this has now been fixed.

c6bbafb516: Updated the default sucrase-based Jest transform to include source maps if the environment variable ENABLE_SOURCE_MAPS is non-empty. This can be used to better support editor test debugging integrations.

7410e12268: The test command now automatically adds --passWithNoTests to the Jest invocation. To revert this behavior, pass --passWithNoTests=false or --no-passWithNoTests.

Updated dependencies

@backstage/config-loader@0.9.4

@backstage/errors@0.2.1

@backstage/release-manifests@0.0.2

@backstage/cli-common@0.1.7

@backstage/config@0.1.14

@backstage/types@0.1.2

0.13.2

Patch Changes

bbbaa8ed61: The plugin:diff command no longer validates the existence of any of the files within dev/ or src/.

eaf67f0578: Introduced initial support for an experimental backstage.role field in package.json, as well as experimental and hidden migrate and script sub-commands. We do not recommend usage of any of these additions yet.

aeb5c69abb: Introduces a new --release parameter to the backstage-cli versions:bump command. The release can be either a specific version, for example 0.99.1, or the latest main or next release. The default behavior is to bump to the latest main release.

d59b90852a: The experimental types build enabled by --experimental-type-build now runs in a separate worker thread.

50a19ff8dd: The file path printed by the default lint formatter is now relative to the repository root, rather than the individual package.

63181dee79: Tweaked frontend bundling configuration to avoid leaking declarations into global scope.

... (truncated)

Commits

See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

container-registry / backstage-plugin-harbor-backend

Bump @backstage/cli from 0.10.5 to 0.14.0 #35

0.14.0

Minor Changes

Patch Changes

0.13.2

Patch Changes