Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): update module golang.org/x/crypto to v0.20.0 #507

Merged
merged 1 commit into from
Mar 2, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 29, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
golang.org/x/crypto v0.19.0 -> v0.20.0 age adoption passing confidence

Configuration

📅 Schedule: Branch creation - "on the 1st day of the month" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Feb 29, 2024
@renovate renovate bot force-pushed the renovate/golang.org-x-crypto-0.x branch 3 times, most recently from 68bc6fd to dea9407 Compare March 1, 2024 23:26
@renovate renovate bot force-pushed the renovate/golang.org-x-crypto-0.x branch from dea9407 to f3e8535 Compare March 1, 2024 23:33
@trim21 trim21 merged commit 7cd92e9 into master Mar 2, 2024
4 checks passed
@trim21 trim21 deleted the renovate/golang.org-x-crypto-0.x branch March 2, 2024 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file size/S size/XS
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant