Skip to content

Conversation

@renovate-bot
Copy link
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
github.com/go-git/go-git/v5 v5.13.2 -> v5.14.0 age adoption passing confidence require minor
github.com/googleapis/enterprise-certificate-proxy v0.3.4 -> v0.3.5 age adoption passing confidence require patch
golang.org/x/oauth2 v0.26.0 -> v0.27.0 age adoption passing confidence require minor
google.golang.org/genproto/googleapis/bytestream 9fdb1ca -> 55c9018 age adoption passing confidence require digest
google.golang.org/genproto/googleapis/rpc 9fdb1ca -> 55c9018 age adoption passing confidence require digest

Release Notes

go-git/go-git (github.com/go-git/go-git/v5)

v5.14.0

Compare Source

What's Changed

⚠️ Note that this version requires Go 1.23, due to the bump to golang.org/x/[email protected] which mitigates the CVE above. User's that can't bump to Go 1.23 will need to remain on the previous v5.13.x release.

Full Changelog: go-git/go-git@v5.13.2...v5.14.0

googleapis/enterprise-certificate-proxy (github.com/googleapis/enterprise-certificate-proxy)

v0.3.5

Compare Source

This release bumps Golang version to 1.23 and crypto to 0.35.0 to be compliant with CVE scanner.

What's Changed

New Contributors

Full Changelog: googleapis/enterprise-certificate-proxy@v0.3.4...v0.3.5


Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), 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 was generated by Mend Renovate. View the repository job log.

@renovate-bot renovate-bot requested a review from a team as a code owner March 3, 2025 03:15
@forking-renovate
Copy link

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 1 additional dependency was updated

Details:

Package Change
golang.org/x/crypto v0.33.0 -> v0.35.0
File name: internal/kokoro/discogen/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 7 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.22.7 -> 1.23.6
github.com/Microsoft/go-winio v0.6.1 -> v0.6.2
github.com/cloudflare/circl v1.3.7 -> v1.6.0
github.com/cyphar/filepath-securejoin v0.3.6 -> v0.4.1
github.com/golang/groupcache v0.0.0-20210331224755-41bb18bfe9da -> v0.0.0-20241129210726-2c02b8208cf8
github.com/skeema/knownhosts v1.3.0 -> v1.3.1
golang.org/x/crypto v0.32.0 -> v0.35.0
golang.org/x/net v0.34.0 -> v0.35.0

@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Mar 3, 2025
@kokoro-team kokoro-team removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Mar 3, 2025
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Mar 3, 2025
@codyoss codyoss added the automerge Merge the pull request once unit tests and other checks pass. label Mar 3, 2025
@kokoro-team kokoro-team removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Mar 3, 2025
@gcf-merge-on-green gcf-merge-on-green bot merged commit e878018 into googleapis:main Mar 3, 2025
4 checks passed
@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Mar 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants