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

Upgrade: Bump github.com/google/go-containerregistry from 0.20.2 to 0.20.3 #263

Open
wants to merge 1 commit into
base: pre-main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 3, 2025

Bumps github.com/google/go-containerregistry from 0.20.2 to 0.20.3.

Release notes

Sourced from github.com/google/go-containerregistry's releases.

v0.20.3

What's Changed

New Contributors

Full Changelog: google/go-containerregistry@v0.20.2...v0.20.3

Commits

Dependabot compatibility score

Dependabot 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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [github.com/google/go-containerregistry](https://github.com/google/go-containerregistry) from 0.20.2 to 0.20.3.
- [Release notes](https://github.com/google/go-containerregistry/releases)
- [Changelog](https://github.com/google/go-containerregistry/blob/main/.goreleaser.yml)
- [Commits](google/go-containerregistry@v0.20.2...v0.20.3)

---
updated-dependencies:
- dependency-name: github.com/google/go-containerregistry
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Feb 3, 2025
Copy link

guardrails bot commented Feb 3, 2025

⚠️ We detected 2 security issues in this pull request:

Vulnerable Libraries (2)
Severity Details
Medium pkg:golang/golang.org/x/[email protected] upgrade to: > v0.34.0
Critical pkg:golang/github.com/google/[email protected] upgrade to: > v0.20.3

More info on how to fix Vulnerable Libraries in Go.


👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

Copy link

dryrunsecurity bot commented Feb 3, 2025

DryRun Security Summary

The code changes involve updating dependency versions in go.sum and go.mod files, including modifications to cloud packages, container registry libraries, and monitoring tools, while also updating the Go version from 1.23 to 1.23.2, representing a routine maintenance update for improved security and functionality.

Expand for full summary

Summary:

The provided code changes primarily involve updates to the go.sum and go.mod files, which manage the dependencies used in the Go project. The changes update the versions of several dependencies, including cloud-related packages, container registry libraries, compression utilities, and various other Go-related packages.

From an application security perspective, these dependency updates are generally a positive change, as they often include security fixes and improvements. However, it's important to review the specific changes in each dependency to ensure there are no known vulnerabilities or breaking changes that could impact the application.

The update to the go.opentelemetry.io/otel and related packages may also indicate improvements to the application's observability and monitoring capabilities, which can be beneficial for security and performance monitoring.

Overall, this change appears to be a routine update of dependencies, which is a good practice to keep the application secure and up-to-date.

Files Changed:

  1. go.sum: This file has been updated to reflect the new versions of the dependencies used in the project. The changes include updates to the versions of several packages, such as cloud.google.com/go/compute/metadata, github.com/containerd/stargz-snapshotter/estargz, github.com/docker/cli, and others.

  2. go.mod: The go.mod file has been updated to reflect the project name change from github.com/intelops/genval to github.com/intelops/genval, and the Go version has been updated from 1.23 to go1.23.2. Additionally, several dependencies have been updated, including github.com/google/go-containerregistry, github.com/stretchr/testify, and various golang.org/x and go.opentelemetry.io packages.

Code Analysis

We ran 9 analyzers against 2 files and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer Findings
Sensitive Files Analyzer 2 findings

View PR in the DryRun Dashboard.

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 go Pull requests that update Go code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants