v167 was mistakenly tagged in GitHub during the publication process of v163. When 167 was published to the buildpack registry, it ended up pointing to v163 code. I've republished the latest code (including go1.19 from #496) to the registry, where it is now known as 168. Once this is merged, I'll fix the git tags to match this changelog and the buildpack registry.
This also updates the publish script to match that of heroku/heroku-buildpacks-python, which includes a git fetch to prevent problems like these.
v167was mistakenly tagged in GitHub during the publication process ofv163. When167was published to the buildpack registry, it ended up pointing tov163code. I've republished the latest code (including go1.19 from #496) to the registry, where it is now known as168. Once this is merged, I'll fix the git tags to match this changelog and the buildpack registry.This also updates the publish script to match that of heroku/heroku-buildpacks-python, which includes a
git fetchto prevent problems like these.