Ed Morley
Ed Morley
We're encountering this too, in: https://github.com/heroku/builder/actions/runs/6303904793/job/17114118993?pr=392#step:5:9 When running `yq '.stack.run-image' builder-22/builder.toml` against this toml file: https://github.com/heroku/builder/blob/b83a3606a68b882484ee3353a58c2813d321a9f4/builder-22/builder.toml
We've since dropped this as a (transitive) dependency so are no longer using this crate. Closing the PR to clean up my open PRs list.
I'm not against doing so (it would presumably mean we can drop the temporary tags thing too), though: - I see the official Docker images don't do this (eg https://hub.docker.com/_/ubuntu/tags),...
This would resolve the missing arch metadata we're seeing in our (new) multi-arch buildpack images, eg: https://hub.docker.com/repository/docker/heroku/buildpack-go/tags
xref https://github.com/superfly/flyctl/pull/3396
The first item in the Lifecycle todo list above links to a duped issue, so is showing as completed, but that's just because it was closed out as a dupe....
> @edmorley btw, I pushed the undocumented bewit support to PyPI so you can use it more easily. http://mohawk.readthedocs.org/en/latest/#changelog Thank you :-) CC @catlee @jhford
Hmm so this might be fixed by: https://github.com/pypa/hatch/pull/576
Thank you for the fast reply! I'd missed that PEP 639 is still a draft - Hatch's docs suggest using the new string form `project.license` field, so I had presumed...
> We could leave this open as a reminder if/when PEP 639 is accepted, or we could close this for now. Whichever you prefer; either works for me :-)