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

Bump github.com/google/go-containerregistry from 0.12.0 to 0.12.1 #903

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 10, 2022

Bumps github.com/google/go-containerregistry from 0.12.0 to 0.12.1.

Release notes

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

v0.12.1

Changelog

  • 426de7d4 Bump golangci/golangci-lint-action from 3.2.0 to 3.3.0 (#1475)
  • 6442b027 Bump goreleaser/goreleaser-action from 3.1.0 to 3.2.0 (#1476)
  • 76ae8192 Fix context.DeadlineExceeded comparison (#1488)
  • 1711cefd Fix missing body.Close() in bearer auth (#1482)
  • 02f47e13 bump version of slsa generator (#1468)
  • 353a1176 crane: add catalog argument use annotation (#1473)
  • a0cca8a0 k8schain: Log and proceed if secret or SA are not found (#1472)

Container Images

https://gcr.io/go-containerregistry/crane:v0.12.1 https://gcr.io/go-containerregistry/gcrane:v0.12.1

For example:

docker pull gcr.io/go-containerregistry/crane:v0.12.1
docker pull gcr.io/go-containerregistry/gcrane:v0.12.1
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 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.12.0 to 0.12.1.
- [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.12.0...v0.12.1)

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

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot requested a review from a team November 10, 2022 22:02
@dependabot dependabot bot added semver:patch A change requiring a patch version bump type:dependency-upgrade A dependency upgrade labels Nov 10, 2022
@dmikusa dmikusa merged commit 6a1e8d8 into main Nov 12, 2022
@dmikusa dmikusa deleted the dependabot/go_modules/github.com/google/go-containerregistry-0.12.1 branch November 12, 2022 03:04
This was referenced Nov 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
semver:patch A change requiring a patch version bump type:dependency-upgrade A dependency upgrade
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant