Bump @backstage/cli from 0.26.11 to 0.27.0 in /plugins/cad

[dependabot]

Bumps @backstage/cli from 0.26.11 to 0.27.0.

Changelog

Sourced from @​backstage/cli's changelog.

0.27.0

Minor Changes

• 32a38e1: BREAKING: The lockfile (yarn.lock) dependency analysis and mutations have been removed from several commands.

  The versions:bump command will no longer attempt to bump and deduplicate dependencies by modifying the lockfile, it will only update package.json files.

  The versions:check command has been removed, since its only purpose was verification and mutation of the lockfile. We recommend using the yarn dedupe command instead, or the yarn-deduplicate package if you're using Yarn classic.

  The check that was built into the package start command has been removed, it will no longer warn about lockfile mismatches.

  The packages in the Backstage ecosystem handle package duplications much better now than when these CLI features were first introduced, so the need for these features has diminished. By removing them, we drastically reduce the integration between the Backstage CLI and Yarn, making it much easier to add support for other package managers in the future.

Patch Changes

• 7eb08a6: Add frontend-dynamic-container role to eslint config factory
• b2d97fd: Fixing loading of additional config files with new ConfigSources
• fbc7819: Use ES2022 in CLI bundler
• 93095ee: Make sure node-fetch is version 2.7.0 or greater
• 6d898d8: Switched the process polyfill to use require.resolve for greater compatability.
• e53074f: Updated default backend plugin to use RootConfigService instead of Config. This also removes the dependency on @backstage/config as it's no longer used.
• ee2b0e5: The experimental module federation build now has the ability to force the use of development versions of react and react-dom by setting the FORCE_REACT_DEVELOPMENT flag.
• 239dffc: Remove usage of deprecated functionality from @​backstage/config-loader
• e6e7d86: Switched the target from 'ES2022' to 'es2022' for better compatibility with older versions of swc.
• 2ced236: Updated dependency @module-federation/enhanced to 0.3.1
• 0eedec3: Add support for dynamic plugins via the EXPERIMENTAL_MODULE_FEDERATION environment variable when running yarn start.
• adabb40: New command now supports setting package license
• dc4fb4f: Fix for repo build --all not properly detecting the experimental public entry point.
• Updated dependencies
  • @​backstage/config-loader@​1.9.0
  • @​backstage/integration@​1.14.0
  • @​backstage/catalog-model@​1.6.0
  • @​backstage/cli-common@​0.1.14
  • @​backstage/cli-node@​0.2.7
  • @​backstage/config@​1.2.0
  • @​backstage/errors@​1.2.4
  • @​backstage/eslint-plugin@​0.1.8
  • @​backstage/release-manifests@​0.0.11
  • @​backstage/types@​1.1.1

0.27.0-next.4

Patch Changes

• 6d898d8: Switched the process polyfill to use require.resolve for greater compatability.
• 2ced236: Updated dependency @module-federation/enhanced to 0.3.1
• Updated dependencies
  • @​backstage/catalog-model@​1.6.0-next.0
  • @​backstage/cli-common@​0.1.14

... (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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[nephio-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign henderiw for approval by writing /assign @henderiw in a comment. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[nephio-prow]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a nephio-project member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[kmadejek-samsung]

Manual bumping of Backstage modules is not recommended and can lead to build and/or application errors. We should disable Dependabot recommendations for all @backstage packages.

The Backstage CLI has a command to bump all @backstage packages and dependencies you're using to the latest versions (...) The reason for bumping all @backstage packages at once is to maintain the dependencies that they have between each other. By default the bump command will upgrade @backstage packages to the latest main release line which is released monthly.

https://backstage.io/docs/getting-started/keeping-backstage-updated/#updating-backstage-versions-with-backstage-cli

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.