Closed edmorley closed 2 years ago
$ docker pull heroku/procfile-cnb@sha256:74881b33e1e33eea38b419e667b0a99ac50e536727eeefd1b2eeb7ff3a937ffd
docker.io/heroku/procfile-cnb@sha256:74881b33e1e33eea38b419e667b0a99ac50e536727eeefd1b2eeb7ff3a937ffd: Pulling from heroku/procfile-cnb
6493100ee6f6: Pull complete
Digest: sha256:74881b33e1e33eea38b419e667b0a99ac50e536727eeefd1b2eeb7ff3a937ffd
Status: Downloaded newer image for heroku/procfile-cnb@sha256:74881b33e1e33eea38b419e667b0a99ac50e536727eeefd1b2eeb7ff3a937ffd
docker.io/heroku/procfile-cnb@sha256:74881b33e1e33eea38b419e667b0a99ac50e536727eeefd1b2eeb7ff3a937ffd
$ docker tag heroku/procfile-cnb@sha256:74881b33e1e33eea38b419e667b0a99ac50e536727eeefd1b2eeb7ff3a937ffd heroku/procfile-cnb:0.6.1
$ docker pull heroku/procfile-cnb@sha256:79697af377bb9a213a34488253a2ad99e2feb676491bc1f9b6c6fc5418441128
docker.io/heroku/procfile-cnb@sha256:79697af377bb9a213a34488253a2ad99e2feb676491bc1f9b6c6fc5418441128: Pulling from heroku/procfile-cnb
59e6d2310e44: Pull complete
Digest: sha256:79697af377bb9a213a34488253a2ad99e2feb676491bc1f9b6c6fc5418441128
Status: Downloaded newer image for heroku/procfile-cnb@sha256:79697af377bb9a213a34488253a2ad99e2feb676491bc1f9b6c6fc5418441128
docker.io/heroku/procfile-cnb@sha256:79697af377bb9a213a34488253a2ad99e2feb676491bc1f9b6c6fc5418441128
$ docker tag heroku/procfile-cnb@sha256:79697af377bb9a213a34488253a2ad99e2feb676491bc1f9b6c6fc5418441128 heroku/procfile-cnb:1.0.1
$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
heroku/procfile-cnb 0.6.1 fbae847949a2 42 years ago 3.27MB
heroku/procfile-cnb 1.0.1 99aabb9d230c 42 years ago 6.14MB
$ docker push heroku/procfile-cnb:0.6.1
The push refers to repository [docker.io/heroku/procfile-cnb]
a02d3fde2aeb: Layer already exists
0.6.1: digest: sha256:33b050f2dab823890312195f1bf69114570f0d75f2f0d2275b970364f168ce22 size: 527
$ docker push heroku/procfile-cnb:1.0.1
The push refers to repository [docker.io/heroku/procfile-cnb]
a20a2ece31b2: Layer already exists
1.0.1: digest: sha256:5105ff510b24c2e365b313b2caaea0801a512ced4f6efc91d90288fd906703c5 size: 528
On Docker Hub, currently:
0.6.1
tag refers toheroku/procfile-cnb@sha256:2925a3f2091076b0790d248b2daec4c6648f0f000bbd2f824e0e2f3a3e6b1673
1.0.1
tag refers toheroku/procfile-cnb@sha256:e91a145db3075c9819c9eb07c0d9c96262d81ba32cb81f3b1b78a350cfdc3457
However the buildpack registry has the following (source):
0.6.1
:heroku/procfile-cnb@sha256:74881b33e1e33eea38b419e667b0a99ac50e536727eeefd1b2eeb7ff3a937ffd
1.0.1
:heroku/procfile-cnb@sha256:79697af377bb9a213a34488253a2ad99e2feb676491bc1f9b6c6fc5418441128
Judging by the tag publish dates and the GitHub Actions history, it appears the original Docker tags were overwritten accidentally when the next release was due to occur, due to the
buildpack.toml
version not having been bumped (eg #8, #90).In order that the releases are consistent, we should update the Docker tags to match the buildpack registry releases.