chore(deps): bump github.com/GoogleCloudPlatform/docker-credential-gcr from 1.5.1-0.20230328182921-62afb2723512 to 2.0.5+incompatible

[dependabot]

Bumps github.com/GoogleCloudPlatform/docker-credential-gcr from 1.5.1-0.20230328182921-62afb2723512 to 2.0.5+incompatible.

Release notes

Sourced from github.com/GoogleCloudPlatform/docker-credential-gcr's releases.

v2.0.5

Adds new regions for Artifact Registry

• Melbourne == australia-southeast2
• Warsaw == europe-central2
• Delhi == asia-south2

Also gives precedence to the $HOME environment variable when returning the user's home directory. $HOME has precedence over records in the password database since the credential helper may be running under a different UID in a user namespace.

Note: This release is a little busted in that I didn't update the config PatchVersion from 4 -> 5. Sometime in the next couple weeks I'll automate out this config const so we don't run into this issue again.

Archive	binary sha256sum
docker-credential-gcr_linux_386-2.0.5.tar.gz	0cfacee31b77ddc1d25bfc15bd93603c129f8327672ed9330c43afd039f82088
docker-credential-gcr_linux_amd64-2.0.5.tar.gz	a673b3d6e2fddd0fe6baf807f7b11f98714eb5b901b0c27e26cd33b0bc291ad5
docker-credential-gcr_linux_arm64-2.0.5.tar.gz	de0942177e15f4f087812f75fa45bddbd11a970ed36f3ed991592ceddb84236b
docker-credential-gcr_darwin_amd64-2.0.5.tar.gz	82aaabe879fb05acb4599f716a645d988cb1b81d49d114f04037ebdb1588db43
docker-credential-gcr_darwin_arm64-2.0.5.tar.gz	4b1b1d28cb661e4fd98372799906cc30045c3bc781237dccf5d9312bbe688c59
docker-credential-gcr_windows_386-2.0.5.tar.gz	d6db1d16800be0df8af28dd492afb1f693890e321be49a26506c4c9e6eb04c14
docker-credential-gcr_windows_amd64-2.0.5.tar.gz	62603a2f6d7c322bba37e8b8b952c8882b23b84d0cb8456c5b86aaab0997d46c

v2.0.4

Adds new regions for Artifact Registry:

• asia-northeast3
• us-west3
• us-west4
• asia-southeast2

Archive	sha256sum
docker-credential-gcr_darwin_amd64-2.0.4.tar.gz	fb37bc90831807ccfda115fa8fbc27fd6564f085c5eb258962b3582b60e1ea71
docker-credential-gcr_darwin_arm64-2.0.4.tar.gz	170b3ce008d33caaf2347fb39b8ad23e6e3d9b00790304f531e6a37564806f41
docker-credential-gcr_linux_386-2.0.4.tar.gz	932a07a4a77741801f2d4067dcf113be4e27f54c525f618f2dee2799a00765d6
docker-credential-gcr_linux_amd64-2.0.4.tar.gz	4fca8441c41802f4bcc4912672c55d4b1232decb90639f8a684d3b389e4e6e91
docker-credential-gcr_linux_arm64-2.0.4.tar.gz	9276eab0d6da985f01f5f0d6d00313c9a49768d4eb0112b5fb8b4fdda07d1f7d
docker-credential-gcr_windows_386-2.0.4.tar.gz	2a4e825b63c845d2e96d6d871926ef9c51a95a62a288b1e05b06019ededc7bd9
docker-credential-gcr_windows_amd64-2.0.4.tar.gz	fa8bd855ba23e7668b48381e8ac7ba2b42c311ae3c26b0ab662d5b212b25255d

v2.0.2

Adds the --include-artifact-registry flag which will add all Artifact Registry registries to the credential config file. This is only intended for tooling that needs to ensure that it sends credentials to any Artifact Registry endpoint when pulling images.

Note that adding a long list of registries to the config file will slow down docker build. The recommendation for users is to only add the registries that are being used, by passing them using the --registries flag.

Archive	sha256sum
docker-credential-gcr_darwin_386-2.0.2.tar.gz	1c925d97d6409d775650b0f085a688a7077e07cf3ddf0a8cdc6dd1ceb85f449e
docker-credential-gcr_darwin_amd64-2.0.2.tar.gz	629577fcbb781ef7f8e751241fbc149a56bb52320d6c0cba995fffaa23fa009d
docker-credential-gcr_linux_386-2.0.2.tar.gz	6defbe32e44444795308c82ec7d588ba29fb464b571fd87c7374a011702a088f
docker-credential-gcr_linux_amd64-2.0.2.tar.gz	12a4d75885a29b183bb28ff469f5ca40ef148f195b4bbd5bb27f5a9cdd8dea2f
docker-credential-gcr_windows_386-2.0.2.tar.gz	210602b2732742438df92e5c192a46b994b8402bf954ff0cf3418b7deba5fa76

... (truncated)

Commits

• See full diff in compare view

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)

[liam-verta]

Despite the numbering v2.0.5+incompatible is actually an older version than v1.5.1-0.20230328182921-62afb2723512. See #2562. Suggest closing this PR.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.