Migrate away from deprecated `heroku/buildpacks:20` CNB builder image

Open
#2,964 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Domain
build-system

Research direction

Search the flyctl repository for heroku/buildpacks:20 and the related builder references shown in the issue. Replace deprecated builder usage with a supported Heroku builder image, then verify that no deprecated references remain in the repository.

Written by the indexing model from the issue text.

Description

bug

Hi 👋

This project uses Heroku's heroku/buildpacks:20 CNB builder image:
https://github.com/search?q=repo%3Asuperfly%2Fflyctl%20(heroku%2Fbuilder-classic%20OR%20heroku%2Fbuildpacks)&type=code

We have deprecated this builder image as of https://github.com/heroku/cnb-builder-images/pull/429.

Please migrate to heroku/builder:22 or heroku/builder:20, to continue to receive security updates, and to avoid disruption when the build time deprecation warning is upgraded to an error in the future.

More information on the difference between the various builder images can be seen here:
https://github.com/heroku/cnb-builder-images#heroku-cnb-builder-images

Dominant language
Go
Stars
1.7k
Forks
311
Avg merge
12h 50m
Merged PRs (30d)
78

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from superfly/flyctl

All issues in superfly/flyctl

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.