Ed Morley

Unexpected `failed to select a version for the requirement` for workspace `cargo release publish`

3

We're considering switching to cargo-release to perform the publish part of our two-stage release process. I just ran a dry-run `cargo release publish` locally on a branch with this change...

Heroku CLI commands Dev Center page is out of date

1

**This project is for the Heroku CLI only and issues are reviewed as we are able. If you need more immediate assistence or help with anything not specific to the...

Stop installing setuptools and wheel by default

3

Currently `get-pip.py` installs not only pip, but also setuptools and wheel by default, unless the `--no-setuptools` / `--no-wheel` (or `PIP_NO_SETUPTOOLS` / `PIP_NO_WHEEL` env vars) are used. This has historically been...

Add history metadata to layers created by `pack builder create`

1

### Description Currently builder images created using `pack builder create` have blank descriptions for each layer when the builder is inspected using `docker history `. This also causes the Docker...

Allow omitting buildpack version when using `pack builder create --flatten`

4

### Description Currently the new `--flatten` feature of `pack builder create` is a bit awkward to use, since it requires that the list of passed buildpacks include the exact buildpack...

The lifecycle Buildpack API support matrix here says that lifecycle 0.19.0 supports Buildpack API 0.11: https://github.com/buildpacks/lifecycle/blob/435d226f1ed54b0bec806716ba79e14a2a093736/README.md#supported-apis ...however, lifecycle 0.19.0 does not support it, since `0.11` is not present in the...

Buildpack API deprecation warning not shown for transitive dependency buildpacks

4

### Summary If a buildpack is using a deprecated Buildpack API version, `lifecycle` outputs a warning like so during detect: ``` ===> DETECTING Warning: Buildpack 'heroku/[email protected]' requests deprecated API '0.6'...

Initial experimental (since Ubuntu 24.04 isn't even GA itself yet) Heroku-24 images were added in #245. In that PR, a few packages were dropped compared to Heroku-22, to try and...

Support PEP 639 license metadata once that PEP is accepted

7

This project has a `license` defined under the `[project]` table in `pyproject.toml`: https://github.com/heroku/sf-functions-python/blob/a7541831525ae1850ae2c8511d2b0c8f94597a53/pyproject.toml#L10 However, pyroma 4.1 on macOS using Python 3.11.0 reports that no license was specified: ``` $ pyroma...

Restores the specification for `CNB_STACK_ID` to the definition that was used prior to the docs refactor in #335. Fixes #396. Backport of #397.