Bump @octokit/request-error and @backstage/cli

[dependabot]

Bumps @octokit/request-error to 5.1.1 and updates ancestor dependency @backstage/cli. These dependencies need to be updated together.

Updates @octokit/request-error from 3.0.3 to 5.1.1

Release notes

Sourced from @​octokit/request-error's releases.

v5.1.1

5.1.1 (2025-02-14)

Bug Fixes

• ReDos regex vulnerability, reported by @​dayshift (12a14f0)

v5.1.0

5.1.0 (2024-04-05)

Bug Fixes

• upgrade @octokit/types to v13 (3af20bd)

Features

• security: Add provenance (#416) (94147e8)

v5.0.1

5.0.1 (2023-09-23)

Bug Fixes

• deps: update dependency @​octokit/types to v12 (#366) (590fc39)

v5.0.0

5.0.0 (2023-07-07)

Bug Fixes

• deps: update dependency @​octokit/types to v11 (#348) (372097e)

BREAKING CHANGES

• deps: upgrade @octokit/types to v11

v4.0.2

4.0.2 (2023-06-16)

Bug Fixes

• deps: update dependency @​octokit/types to v10 (#343) (28b1958)

... (truncated)

Commits

• b51ed27 test: ReDos regex vulnerability, reported by @​dayshift
• 12a14f0 fix: ReDos regex vulnerability, reported by @​dayshift
• 3af20bd fix: upgrade @octokit/types to v13
• 94147e8 feat(security): Add provenance (#416)
• 590fc39 fix(deps): update dependency @​octokit/types to v12 (#366)
• 4b9c57e ci(action): update peter-evans/create-or-update-comment digest to 46da6c0
• 710afc3 ci(action): update peter-evans/create-or-update-comment digest to 1f6c514
• c82c8ce ci(action): update peter-evans/create-or-update-comment digest to 223779b
• ec24ead ci(action): update peter-evans/create-or-update-comment digest to 46846e5 (#362)
• 365f18d ci(action): update actions/checkout action to v4
• Additional commits viewable in compare view

Updates @backstage/cli from 0.34.4 to 0.36.4

Changelog

Sourced from @​backstage/cli's changelog.

0.36.4

Patch Changes

• 61d4881: The shared ESLint configuration now reports unused imports in config.d.ts configuration schema files. These declaration files are not covered by the TypeScript compiler's unused-variable checks, which previously allowed a stray import to slip through. Such an import can resolve during local development but break configuration schema loading for consumers of the published package, so it is now caught at lint time.
• Updated dependencies
  • @​backstage/cli-module-build@​0.1.5
  • @​backstage/cli-common@​0.3.0
  • @​backstage/cli-defaults@​0.1.4
  • @​backstage/cli-module-test-jest@​0.1.4
  • @​backstage/cli-node@​0.3.4

0.36.4-next.2

Patch Changes

• Updated dependencies
  • @​backstage/cli-common@​0.3.0-next.0
  • @​backstage/cli-module-build@​0.1.5-next.2
  • @​backstage/cli-module-test-jest@​0.1.4-next.0
  • @​backstage/cli-node@​0.3.4-next.0
  • @​backstage/cli-defaults@​0.1.4-next.1

0.36.4-next.1

Patch Changes

• 61d4881: The shared ESLint configuration now reports unused imports in config.d.ts configuration schema files. These declaration files are not covered by the TypeScript compiler's unused-variable checks, which previously allowed a stray import to slip through. Such an import can resolve during local development but break configuration schema loading for consumers of the published package, so it is now caught at lint time.
• Updated dependencies
  • @​backstage/cli-module-build@​0.1.5-next.1

0.36.4-next.0

Patch Changes

• Updated dependencies
  • @​backstage/cli-module-build@​0.1.5-next.0
  • @​backstage/cli-defaults@​0.1.4-next.0

0.36.3

Patch Changes

• b521571: Improved validation of conflicting CLI module commands, including conflicts between parent and nested command paths.
• Updated dependencies
  • @​backstage/cli-module-build@​0.1.4
  • @​backstage/cli-module-test-jest@​0.1.3
  • @​backstage/cli-node@​0.3.3
  • @​backstage/eslint-plugin@​0.3.1
  • @​backstage/cli-defaults@​0.1.3

... (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 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 duplication

Metric	Results
Duplication	0

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

Codacy analysis indicates that the PR is up to standards with no new quality issues. However, there is a discrepancy between the PR title and the changes in the package manifest: one of the mentioned dependencies is not explicitly updated in the manifest, likely appearing only in the lock file. Since this involves a major version change, it is important to ensure that no breaking changes affect the project, especially if the dependency is referenced directly. There are currently no unit tests visible in the diff to verify the impact of these updates.

About this PR

• The update to one of the dependencies mentioned in the title is not visible in the package manifest diff. If this was intended to be a direct dependency update, please ensure it is added to the manifest. If it is a transitive update, verify that the major version jump does not introduce breaking changes in parts of the codebase that might reference it.

Test suggestions

• Verify that the application builds and all existing tests pass with the updated dependencies.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify that the application builds and all existing tests pass with the updated dependencies.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}