Repository navigation
Conversation
The 2.0.0 release was tagged at the release PR's merge commit, but the CD run that created it was triggered by the next push (#661). The publish job checked out the triggering commit, so setuptools_scm versioned the build 2.0.1.dev1 and that went to PyPI instead of 2.0.0. Check out release-please's tag_name, or a new tag input when force publishing by hand, and fall back to the triggering commit.
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The 2.0.0 release went to PyPI as
runpod 2.0.1.dev1, not 2.0.0.What happened
v2.0.0at chore(main): release 2.0.0 #594's merge commit (e3ad2ee).a4ba078). Before ci: run workflows on Blacksmith runners #661, CD couldn't get past the IP allow list.pypi-publishchecked out the triggering commit. The version comes fromsetuptools_scm, so one commit past the tag built as2.0.1.dev1(run).Checked locally:
setuptools_scmgives2.0.0atv2.0.0and2.0.1.dev1ata4ba078.Change
pypi-publishchecks outneeds.release-please.outputs.tag_name, so a release always builds from its tag.taginput onworkflow_dispatchlets a force publish build a given tag.After merge
Publish 2.0.0 from its tag:
A PyPI maintainer should yank
2.0.1.dev1. pip skips.devversions by default, sopip install runpodstill resolves to 1.12.0 until 2.0.0 is published.Test plan
refand thetaginput are as listedsetuptools_scmversion atv2.0.0is2.0.0runpod 2.0.0to PyPI🤖 Generated with Claude Code