build(deps): bump github.com/Azure/azure-sdk-for-go/sdk/azcore from 1.21.0 to 1.21.1 in the azure-github-dependencies group across 1 directory

[dependabot]

Bumps the azure-github-dependencies group with 1 update in the / directory: github.com/Azure/azure-sdk-for-go/sdk/azcore.

Updates github.com/Azure/azure-sdk-for-go/sdk/azcore from 1.21.0 to 1.21.1

Release notes

Sourced from github.com/Azure/azure-sdk-for-go/sdk/azcore's releases.

sdk/azcore/v1.21.1

1.21.1 (2026-04-16)

Bugs Fixed

• Fixed an issue in ResponseError.Error() where the request URL path was being logged unescaped.
• Redact query parameters when logging errors.
• For runtime.JoinPaths, don't add a slash between root and paths when paths starts with ? (query string).

Other Changes

• Upgraded to Go 1.25.0.
• Upgraded dependencies.

Commits

• 63e4ba1 Bump release date for azcore (#26613)
• fa03121 remove bypass local dns (#26609)
• c47f9a6 Sync eng/common directory with azure-sdk-tools for PR 15153 (#26607)
• 88b8b5b Changelog for v2.2.0 (#26567)
• 72ca19a Storage STG 101 (#26568)
• b64baf5 Sync .github directory with azure-sdk-tools repository (#26600)
• ecd64dd Prep azcore@v1.21.1 for release (#26596)
• 1d02f20 Update copilot code review instructions and migration breaking change mitigat...
• f6e9ce3 Sync eng/common directory with azure-sdk-tools for PR 14973 (#26531)
• d5a3baf Update CODEOWNERS to remove one owner from Custom Providers (#26588)
• Additional commits viewable in compare view

Summary by CodeRabbit

• Chores
  • Updated Azure SDK core libraries for improved stability, reliability, and downstream bug fixes.

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates two Azure SDK entries in go.mod: the direct dependency github.com/Azure/azure-sdk-for-go/sdk/azcore is bumped from v1.21.0 to v1.21.1, and the indirect dependency github.com/Azure/azure-sdk-for-go/sdk/internal is bumped from v1.11.2 to v1.12.0. No other module versions or replace directives were changed.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title accurately describes the main change: bumping the Azure SDK azcore dependency from v1.21.0 to v1.21.1, which matches the primary change shown in the summary.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dependabot/go_modules/azure-github-dependencies-e1ec8e18a7

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci]

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

I'm waiting for a openshift 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.

Details

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-sigs/prow repository.

[hypershift-jira-solve-ci]

Both failures are now fully understood. Here is the final report:

Test Failure Analysis Complete

Job Information

• Prow Job: pull-ci-openshift-hypershift-main-images
• Build ID: 2052555356319518720
• PR: build(deps): bump github.com/Azure/azure-sdk-for-go/sdk/azcore from 1.21.0 to 1.21.1 in the azure-github-dependencies group across 1 directory #8460 — build(deps): bump github.com/Azure/azure-sdk-for-go/sdk/azcore from 1.21.0 to 1.21.1 in the azure-github-dependencies group
• GitHub Actions Job: gitlint / Gitlint (run 25530735061)

Test Failure Analysis

Error

ci/prow/images:
  step [release-inputs:latest] failed: failed to wait for importing imagestreamtags on
  ci-op-1rqp1k6g/stable: failed to reimport the tag ci-op-1rqp1k6g/stable:vcf-migration-operator:
  unable to import tag ci-op-1rqp1k6g/stable:vcf-migration-operator with message
  Internal error occurred: [dockerimage.image.openshift.io
  "quay.io/openshift/ci:ocp_5.0_vcf-migration-operator" not found,
  dockerimage.image.openshift.io
  "quay-proxy.ci.openshift.org/openshift/ci:ocp_5.0_vcf-migration-operator" not found]
  on the image stream even after (6) imports: timed out waiting for the condition

gitlint / Gitlint:
  3: B1 Line exceeds max length (147>140): "Bumps the azure-github-dependencies group
  with 1 update: [github.com/Azure/azure-sdk-for-go/sdk/azcore](https://github.com/Azure/azure-sdk-for-go)."

Summary

Both failures are unrelated to the dependency bump itself — the Go code changes (bumping azcore from 1.21.0 to 1.21.1) are not the cause. The Prow ci/prow/images job failed because the CI infrastructure could not import the vcf-migration-operator image from the OCP 5.0 release stream — this image does not exist at quay.io/openshift/ci:ocp_5.0_vcf-migration-operator or its proxy. This is a transient CI infrastructure / release-stream configuration issue, not a code defect. The gitlint failure is caused by Dependabot's auto-generated commit body containing a 147-character line that exceeds the repository's 140-character gitlint limit.

Root Cause

ci/prow/images — CI infrastructure issue (not caused by this PR):

The pull-ci-openshift-hypershift-main-images job builds all image targets (hypershift-operator, hypershift, hypershift-tests, hypershift-cli) and then assembles a release snapshot from ocp/5.0. All four image builds succeeded (hypershift-tests in 8m39s, hypershift in 4m6s, hypershift-operator in 5m7s, hypershift-cli in 1m13s). The failure occurred in the [release-inputs:latest] step which imports all OCP 5.0 component images into a CI imagestream. The image ocp_5.0_vcf-migration-operator does not exist at either quay.io/openshift/ci:ocp_5.0_vcf-migration-operator or quay-proxy.ci.openshift.org/openshift/ci:ocp_5.0_vcf-migration-operator. After 6 retry attempts, the import timed out. This is either a newly-added component whose image has not been published yet, or a release-stream configuration referencing a component that has been removed or renamed. This failure would affect any PR running this job — it is not specific to this dependency bump.

gitlint / Gitlint — Dependabot commit message formatting:

Dependabot auto-generates the commit body with the line: Bumps the azure-github-dependencies group with 1 update: [github.com/Azure/azure-sdk-for-go/sdk/azcore](https://github.com/Azure/azure-sdk-for-go). This line is 147 characters, exceeding the repository's gitlint B1 rule maximum of 140 characters. This is a known recurring issue with Dependabot PRs when the dependency name and URL are long enough to exceed the line limit.

Recommendations

1. ci/prow/images: Retry the job — if the vcf-migration-operator image has since been published, the job will pass. If it continues to fail, the OCP 5.0 release-stream configuration needs to be fixed (this is an infrastructure issue in openshift/release or the component team's build pipeline, not in this PR).

2. gitlint / Gitlint: Either:

   • Amend the Dependabot commit message to wrap the long line in the body (line 3) below 140 characters, or
   • Override/dismiss the gitlint check — this is a cosmetic commit-message lint failure on an auto-generated Dependabot PR, and the content change is valid.
   • Alternatively, consider adjusting the .gitlint configuration to increase max-line-length or add an exception for Dependabot commits.

3. Neither failure is caused by the actual code change (bumping azcore 1.21.0 → 1.21.1). The dependency bump itself is safe to merge once these orthogonal issues are resolved.

Evidence

Evidence	Detail
Prow job name	pull-ci-openshift-hypershift-main-images
Build ID	2052555356319518720
All image builds	✅ Succeeded: hypershift-operator, hypershift, hypershift-tests, hypershift-cli
Failing step	[release-inputs:latest] — release image assembly, not code compilation
Missing image	quay.io/openshift/ci:ocp_5.0_vcf-migration-operator (not found after 6 import retries)
Error reason	creating_release_images — CI could not assemble the OCP 5.0 release snapshot
Gitlint rule violated	B1 — body line max length (147 > 140)
Offending gitlint line	Bumps the azure-github-dependencies group with 1 update: [github.com/Azure/azure-sdk-for-go/sdk/azcore](https://github.com/Azure/azure-sdk-for-go).
Line length measured	147 characters (limit: 140)
Commit author	dependabot[bot] — auto-generated commit message
PR code change	Only go.mod / go.sum updates for azcore 1.21.0 → 1.21.1

---

[jparrill]

Looks like the new GH workflow with

• .github/workflows/dependabot-commit-fix.yaml
• .github/workflows/dependabot-commit-fix-reusable.yaml

Is not working as expected due to an issue explained at #8476.

[jparrill]

@dependabot rebase

[dependabot]

Sorry, only users with push access can use that command.

[csrwng]

@dependabot rebase

[openshift-ci]

@dependabot[bot]: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

[jparrill]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dependabot[bot], jparrill

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [jparrill]

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

[dependabot]

Looks like github.com/Azure/azure-sdk-for-go/sdk/azcore is updatable in another way, so this is no longer needed.