[deanq]

The 2.0.0 release went to PyPI as runpod 2.0.1.dev1, not 2.0.0.

What happened

• release-please tagged v2.0.0 at chore(main): release 2.0.0 #594's merge commit (e3ad2ee).
• The CD run that did it was triggered by the next push, ci: run workflows on Blacksmith runners #661 (a4ba078). Before ci: run workflows on Blacksmith runners #661, CD couldn't run on ubuntu-latest.
• pypi-publish checked out the triggering commit. The version comes from setuptools_scm, so one commit past the tag built as 2.0.1.dev1 (run).

Checked locally: setuptools_scm gives 2.0.0 at v2.0.0 and 2.0.1.dev1 at a4ba078.

Change

• pypi-publish checks out needs.release-please.outputs.tag_name, so a release always builds from its tag.
• A new tag input on workflow_dispatch lets a force publish build a given tag.
• Without either, it falls back to the triggering commit, as before.

Status

The 2.0.0 fallout has since been cleaned up by hand: runpod 2.0.0 was force-published from its tag on 2026-10-30, and 2.0.1.dev1 is yanked. Releases 2.1.0 through 2.2.1 published correctly because CD happened to run on each release commit.

This change is still needed as a guardrail: pypi-publish on main still checks out the triggering commit, so any release whose CD run is triggered by a later push (for example after a CD outage, as with 2.0.0) would publish a .devN version again.

Test plan

• Workflow YAML parses; checkout ref and the tag input are as listed
• setuptools_scm version at v2.0.0 is 2.0.0
• PyPI: 2.0.0 is published and 2.0.1.dev1 is yanked (done by hand, no longer needed from this PR)

[Copilot]

🟢 Approval recommended

No active review issues were identified for the release-tag-aware PyPI publishing change.

No open issues 🎉

What changed in this PR

Updates PyPI publishing to build from the release tag, preventing later triggering commits from producing unintended .devN package versions.

Changes:

• Uses the release-please tag as the preferred checkout reference.
• Adds an optional tag input for manual force publishing.
• Preserves the triggering commit as the fallback when neither tag is provided.

File	Description
.github/​workflows/​cd.yml	Adds the manual tag input and tag-aware checkout for production PyPI publishing.

_{Review effort: Balanced}