Bump @backstage/integration from 1.18.1 to 1.20.1

[dependabot]

Bumps @backstage/integration from 1.18.1 to 1.20.1.

Changelog

Sourced from @​backstage/integration's changelog.

@​backstage/integration

2.0.3

Patch Changes

• a07e6a3: Added the correctly-spelled AzureBlobStorageIntegration class export and deprecated the previous typoed AzureBlobStorageIntergation export. Existing usage of AzureBlobStorageIntergation continues to work; switch to AzureBlobStorageIntegration to avoid future removal.
• b75158b: Adapted Azure-related tests for the Azure SDK upgrade to ESM-style exports. The AzureBlobStorageUrlReader now accepts an optional createContainerClient dependency for testability without needing to mock the @azure/storage-blob module.
• 241d359: Changed visibility of Bitbucket username as it is not a secret.

2.0.3-next.1

Patch Changes

• b75158b: Adapted Azure-related tests for the Azure SDK upgrade to ESM-style exports. The AzureBlobStorageUrlReader now accepts an optional createContainerClient dependency for testability without needing to mock the @azure/storage-blob module.
• 241d359: Changed visibility of Bitbucket username as it is not a secret.

2.0.3-next.0

Patch Changes

• a07e6a3: Added the correctly-spelled AzureBlobStorageIntegration class export and deprecated the previous typoed AzureBlobStorageIntergation export. Existing usage of AzureBlobStorageIntergation continues to work; switch to AzureBlobStorageIntegration to avoid future removal.

2.0.2

Patch Changes

• 6b112d3: Fixed two issues in the GitLab integration's fetch behavior:

  • The internal fetch wrapper was passing mode: 'same-origin' on every request. This had no practical effect server-side, but would have caused cross-origin requests to be rejected when the integration is used from a browser. Requests now use the default fetch mode and work correctly in both browser and Node environments.
  • When retries are configured, transient network errors (such as dropped connections or DNS hiccups) are now retried using the same maxRetries and exponential delay as retryable HTTP status codes. Previously, a thrown fetch error would propagate immediately on the first failure regardless of the retry configuration. Caller-initiated aborts continue to surface immediately without being retried.

• b62781f: Moved registerMswTestHooks to test files.

• Updated dependencies

  • @​backstage/errors@​1.3.1
  • @​backstage/config@​1.3.8

2.0.2-next.1

Patch Changes

• 6b112d3: Fixed two issues in the GitLab integration's fetch behavior:

  • The internal fetch wrapper was passing mode: 'same-origin' on every request. This had no practical effect server-side, but would have caused cross-origin requests to be rejected when the integration is used from a browser. Requests now use the default fetch mode and work correctly in both browser and Node environments.
  • When retries are configured, transient network errors (such as dropped connections or DNS hiccups) are now retried using the same maxRetries and exponential delay as retryable HTTP status codes. Previously, a thrown fetch error would propagate immediately on the first failure regardless of the retry configuration. Caller-initiated aborts continue to surface immediately without being retried.

2.0.2-next.0

Patch Changes

... (truncated)

Commits

• c8a8aac Version Packages
• 4aa43f6 chore(deps): update dependency cross-fetch to v4
• f577e11 Version Packages (next)
• 11153a0 Merge remote-tracking branch 'upstream/master' into entra-rename
• ad7d38c fix tests
• 243c655 Updated Azure Active Directory to Entra ID
• 8cdb8c2 Version Packages
• e43d3eb Version Packages (next)
• 0b55f77 Removed some unused dependencies
• bea3617 Version Packages (next)
• Additional commits viewable 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.

[github-actions]

@dependabot merge

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

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

The pull request is currently empty and does not include any file modifications. As a result, the update to the dependency manifest has not been implemented, and the acceptance criteria remain unaddressed. Although the analysis tools report that the project is up to standards, this is a result of the lack of changes rather than a successful implementation. The PR should not be merged until the necessary file updates are provided.

About this PR

• The implementation for the dependency update is missing from the provided code changes. No modifications to package.json or other manifest files were found in the diff.

Test suggestions

• Verify @backstage/integration version is exactly 1.20.1 in package.json

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify @backstage/integration version is exactly 1.20.1 in package.json

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