Previously, docker-credential-gcr would prefer the most 'magical' token sources over more explicit token sources, i.e. environmental sources over gcloud, and gcloud over the credentials stored via docker-credential-gcr gcr-login. This ordering has been reversed, to make debugging more intuitive. See the documentation on GCR credential sources for more information, and how to manually define this preference.

Binary SHA256 Checksums:

• linux-amd64
  • 1ca0b551fb36322c479c08f264e616cc693d4045531586a38b106192016b43ee
• linux-386
  • 2fa922140c1d17c8526a60e58a5735360c67da5432be501f34d5891e3b3a83dd
• darwin-386
  • c98297e7f4a56c597e7d75a0ad6b74a7e0be06d76b5ce8bd665f12eddc7801fd
• darwin-amd64
  • 650dfc817acb52f1f6a42ed8837c2bad2c4aa791a6735f4eb097a5868581a449
• windows-386
  • 1f38568c5df49bb25c98938226759d9ddfd5b7890181c6a06af6c19c85a48915
• windows-amd64
  • 1badf042cea5246143bc14e4dfd8340f9a545e670bf9faaf4ffe94941f12d0cb