chore(deps): bump golang.org/x/crypto from 0.49.0 to 0.52.0 in /cli/azd/extensions/azure.ai.rle#9093
Closed
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.49.0 to 0.52.0. - [Commits](golang/crypto@v0.49.0...v0.52.0) --- updated-dependencies: - dependency-name: golang.org/x/crypto dependency-version: 0.52.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
requested review from
JeffreyCA,
glharper,
trangevi and
trrwilson
as code owners
July 10, 2026 22:07
Contributor
|
Thank you for your contribution @dependabot[bot]! We will review the pull request and get back to you soon. |
JeffreyCA
approved these changes
Jul 15, 2026
Member
Contributor
Author
|
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 If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/go_modules/cli/azd/extensions/azure.ai.rle/golang.org/x/crypto-0.52.0
branch
July 21, 2026 22:58
vhvb1989
added a commit
that referenced
this pull request
Jul 24, 2026
…9240) * chore(deps): group Dependabot security updates into one PR Addresses all open Dependabot alerts across the repo: - cli/azd/extensions/azure.ai.rle: bump golang.org/x/crypto 0.49.0 -> 0.52.0 and golang.org/x/net 0.52.0 -> 0.55.0 (alerts #456-#469). Note x/net requires 0.55.0 for full remediation of #456. - ext/vscode: js-yaml -> 4.3.0, brace-expansion -> 2.1.2 & 5.0.7 (alerts #539, #540, #541) - ext/azuredevops/setupAzd: adm-zip -> 0.6.0, azure-pipelines-task-lib -> 5.278.0, brace-expansion -> 1.1.16 & 2.1.2 (alerts #535, #537, #538) - cli/azd/test/eval: brace-expansion -> 1.1.16 (alert #536) Supersedes and consolidates #9093 and #9215. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 2cef6dea-2ec8-4538-8e55-7a2b0dfa196c * ci: make azdo-extension npm steps non-blocking on PR builds The azdo-extension pipeline currently fails on the self-hosted Linux and Windows agents because they cannot reach registry.npmjs.org (npm EPERM egress block); `npm i -g npm` fails before any dependency is resolved. Build Mac (hosted pool) and the vscode build (same self-hosted pool) are unaffected, confirming this is an agent egress issue, not a code problem. Make the npm-dependent steps (install, test, package) non-blocking for PR validation builds only (Build.Reason == PullRequest) so this gate does not block unrelated PRs such as the grouped Dependabot security update. Release and CD builds on main remain strict, so CodeQL and artifact generation are unaffected. Artifact staging is skipped on PR builds since the package step may not produce a VSIX while the egress issue persists. Tracking issue to fix the egress block and re-enable the gate: #9286 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 2cef6dea-2ec8-4538-8e55-7a2b0dfa196c * ci: trigger azdo pipeline PR validation on build template changes Add the azuredevops build/stage templates to the release-azuredevops pipeline PR and CI path filters so edits to the build job template are validated by the azdo-extension pipeline (previously only changes under ext/azuredevops or the root pipeline file triggered it). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 2cef6dea-2ec8-4538-8e55-7a2b0dfa196c * ci: skip azdo-extension Sign stage on PR builds Now that the BuildAndTest stage completes with issues (instead of hard failing) on PR validation builds while the self-hosted agent npm egress issue persists (#9286), the Sign stage began running on PRs and failed because no vsix artifact is produced on PR builds. Signing is never performed for PR builds, so gate the whole Sign stage to release/CI/manual build reasons. Also add the sign/publish stage templates to the pipeline PR path filters so template changes are validated. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 2cef6dea-2ec8-4538-8e55-7a2b0dfa196c --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 2cef6dea-2ec8-4538-8e55-7a2b0dfa196c
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps golang.org/x/crypto from 0.49.0 to 0.52.0.
Commits
a1c0d99go.mod: update golang.org/x dependencies3c7c869ssh: fix deadlock on unexpected channel responses533fb3fssh: fix source-address critical option bypassabbc44dssh: fix incorrect operator ordere052873ssh: fix infinite loop on large channel writes due to integer overflowb61cf85ssh: enforce user presence verification for security keys9c2cd33ssh: enforce strict limits on DSA key parameters8907318ssh: reject RSA keys with excessively large moduliffd87b4ssh: fix panic when authority callbacks are nil4e7a738ssh: fix deadlock on unexpected global responsesDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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.