@naorpeled v0.44.0 went out with the placeholder tag untagged-64e9bbbb…, so prepare failed the SemVer check and PyPI, Docker and the version bump were all skipped (run 33274135386). PyPI is still on 0.43.0.
- Fix:
gh workflow run publish.yml --ref main -f version=0.44.0. Only the dispatch path runs gh release create, so that is what creates the tag and the release. Main is 3 commits past what the failed run would have built.
- Clear first: the release (375003662), the tag ref it left behind (deleting the release doesn't remove it), and the Release Drafter draft now named
v64.1.0 (379100939), coerced from the placeholder.
Worth automating: the config is fine, tag-template is set, so the placeholder came from the publish step rather than a setting. This is also the third release that needed a manual fix after #2573 (v0.40.0/v0.41.0 missed PyPI) and #2592 (v0.41.1 images never pushed). #2884 puts release-please in place: it keeps an open release PR and creates the tag when that PR merges, with no manual click.
I'm happy to carry that work, though I'd need someone else on the release button — I don't think I have, or should have, tag rights on main.
#2576's reporter was told to try this release; I'll correct that thread once it's out.
@naorpeled v0.44.0 went out with the placeholder tag
untagged-64e9bbbb…, sopreparefailed the SemVer check and PyPI, Docker and the version bump were all skipped (run 33274135386). PyPI is still on 0.43.0.gh workflow run publish.yml --ref main -f version=0.44.0. Only the dispatch path runsgh release create, so that is what creates the tag and the release. Main is 3 commits past what the failed run would have built.v64.1.0(379100939), coerced from the placeholder.Worth automating: the config is fine,
tag-templateis set, so the placeholder came from the publish step rather than a setting. This is also the third release that needed a manual fix after #2573 (v0.40.0/v0.41.0 missed PyPI) and #2592 (v0.41.1 images never pushed). #2884 puts release-please in place: it keeps an open release PR and creates the tag when that PR merges, with no manual click.I'm happy to carry that work, though I'd need someone else on the release button — I don't think I have, or should have, tag rights on main.
#2576's reporter was told to try this release; I'll correct that thread once it's out.