Bump @backstage/cli from 0.10.5 to 0.13.1

dependabot[bot] commented 2 years ago

Bumps @backstage/cli from 0.10.5 to 0.13.1.

Changelog

Sourced from @backstage/cli's changelog.

0.13.1

Patch Changes

5bd0ce9e62: chore(deps): bump inquirer from 7.3.3 to 8.2.0

80f510caee: Log warning if unable to parse yarn.lock

0.13.1-next.1

Patch Changes

5bd0ce9e62: chore(deps): bump inquirer from 7.3.3 to 8.2.0

0.13.1-next.0

Patch Changes

80f510caee: Log warning if unable to parse yarn.lock

0.13.0

Minor Changes

1ddf6d9d5a: Removes the previously deprecated remove-plugin command alongside the --lax option to app:build.

Patch Changes

c372a5032f: chore(deps): bump jest-transform-yaml from 0.1.1 to 1.0.0

1b4ab0d44c: Updated the dependency warning that is baked into app:serve to only warn about packages that are not allowed to have duplicates.

dc46efa2cc: Switched the WebpackDevServer configuration to use client-side detection of the WebSocket protocol.

10086f5873: Upgraded webpack, webpack-dev-server,fork-ts-checker-webpack-plugin, react-dev-utils, and react-hot-loader. Since ForkTsCheckerWebpackPlugin no longer runs ESLint, we now include the ESLintPlugin from eslint-webpack-plugin if the --check flag is passed.

0.12.0

Minor Changes
08fa6a604a: Removed the typescript dependency from the Backstage CLI in order to decouple the TypeScript version in Backstage projects. To keep using a specific TypeScript version, be sure to add an explicit dependency in your root package.json:
  "dependencies": {
    ...
    "typescript": "~4.5.4",
  }
We recommend using a ~ version range since TypeScript releases do not adhere to semver.

It may be the case that you end up with errors if you upgrade the TypeScript version. This is because there was a change to TypeScript not long ago that defaulted the type of errors caught in catch blocks to unknown. You can work around this by adding "useUnknownInCatchVariables": false to the "compilerOptions" in your tsconfig.json:

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