Skip to content

Commit 4246a0b

Browse files
authored
Switch Docker Hub repository to heroku/buildpack-procfile (#219)
To match the naming used by our other CNBs, and the new GitHub repo name for this CNB. The change to the repo metadata here will cause new versions to be published to the new repo instead. The existing tags on the old repo have been copied over already using: `crane copy --all-tags --jobs 1 docker.io/heroku/procfile-cnb docker.io/heroku/buildpack-procfile` (the `--jobs 1` was to ensure the tags appear in the correct order when sorted by push date) See: https://hub.docker.com/r/heroku/procfile-cnb/tags https://hub.docker.com/r/heroku/buildpack-procfile/tags Once this PR has merged, I'll update the index to reference the new repo for old versions too: https://github.com/buildpacks/registry-index/blob/main/pr/oc/heroku_procfile GUS-W-15241542.
1 parent fbb963a commit 4246a0b

File tree

2 files changed

+5
-2
lines changed

2 files changed

+5
-2
lines changed

CHANGELOG.md

+4-1
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
77

88
## [Unreleased]
99

10-
- Changed repository name from `heroku/procfile-cnb` to `heroku/buildpacks-procfile`. ([#216](https://github.com/heroku/buildpacks-procfile/pull/216))
10+
### Changed
11+
12+
- Switched Docker Hub repository from `docker.io/heroku/procfile-cnb` to `docker.io/heroku/buildpack-procfile`. ([#219](https://github.com/heroku/buildpacks-procfile/pull/219))
13+
- Renamed GitHub repository from `heroku/procfile-cnb` to `heroku/buildpacks-procfile`. ([#216](https://github.com/heroku/buildpacks-procfile/pull/216))
1114

1215
## [3.0.0] - 2024-02-28
1316

buildpack.toml

+1-1
Original file line numberDiff line numberDiff line change
@@ -23,4 +23,4 @@ os = "linux"
2323
arch = "amd64"
2424

2525
[metadata.release]
26-
image = { repository = "docker.io/heroku/procfile-cnb" }
26+
image = { repository = "docker.io/heroku/buildpack-procfile" }

0 commit comments

Comments
 (0)