chore(deps): bump golang.org/x/crypto from 0.48.0 to 0.49.0#512
Merged
chore(deps): bump golang.org/x/crypto from 0.48.0 to 0.49.0#512
Conversation
Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.48.0 to 0.49.0. - [Commits](golang/crypto@v0.48.0...v0.49.0) --- updated-dependencies: - dependency-name: golang.org/x/crypto dependency-version: 0.49.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
dependabot
bot
added
dependencies
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Dependency ReviewThe following issues were found:
License Issuesgo.mod
Allowed Licenses: MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC, MPL-2.0, CC0-1.0, Unlicense Excluded from license check: pkg:golang/go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp, pkg:golang/go.opentelemetry.io/otel, pkg:golang/go.opentelemetry.io/otel/metric, pkg:golang/go.opentelemetry.io/otel/trace, pkg:golang/golang.org/x/crypto, pkg:golang/golang.org/x/sys, pkg:golang/golang.org/x/term, pkg:golang/golang.org/x/text, pkg:golang/golang.org/x/time OpenSSF Scorecard
Scanned Files
|
github-merge-queue
bot
removed this pull request from the merge queue due to no response for status checks
2 tasks
github-merge-queue bot
pushed a commit
that referenced
this pull request
Mar 14, 2026
## Summary - Remove `--squash` from auto-merge workflow — the merge queue controls the merge method, passing `--squash` is redundant and may conflict - Add `golang.org/x/term` and `golang.org/x/time` to `allow-dependencies-licenses` in dependency review (compound SPDX expression with Google patent grant, same as other `x/` packages already listed) ## Context All 5 open Dependabot PRs (#512-#516) failed to auto-merge because: 1. The merge queue grouped them together (all modify `go.mod`/`go.sum`), they conflicted, and all got dequeued 2. PR #515 (`golang.org/x/time`) was also blocked by Dependency Review flagging `LicenseRef-scancode-google-patent-license-golang` as incompatible ## Test plan - [ ] CI passes (especially Dependency Review) - [ ] After merge, re-trigger auto-merge on #512-#516 and verify they process through the merge queue one at a time
CybotTM
approved these changes
Mar 14, 2026
|
🚀 Released in v0.21.2 Thank you for your contribution! 🙏 This is now available in the latest release. Please test and verify everything works as expected in your environment. If you encounter any issues, please open a new issue. |
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
1 participant
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.48.0 to 0.49.0.
Commits
982eaa6go.mod: update golang.org/x dependencies159944fssh,acme: clean up tautological/impossible nil conditionsa408498acme: only require prompt if server has terms of servicecab0f71all: upgrade go directive to at least 1.25.0 [generated]2f26647x509roots/fallback: update bundleDependabot 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)