Skip to content

Release workflow: enforce setuptools_scm version and verify wheel + sdist - #606

Merged
abingham merged 1 commit into
masterfrom
codex/investigate-failed-release-ci-job
Aug 9, 2026
Merged

abingham merged 1 commit into
masterfrom
codex/investigate-failed-release-ci-job

Conversation

@abingham

@abingham abingham commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

Motivation

  • Ensure the release build uses the prepared release version and to explicitly verify that both the universal wheel and source distribution are produced and correctly named.

Description

  • Add SETUPTOOLS_SCM_PRETEND_VERSION to the Build distribution step set from needs.prepare.outputs.version so setuptools_scm reports the intended release version during build.
  • Rename the verification step to Verify distribution version and universal wheel and inject a VERSION env from needs.prepare.outputs.version.
  • Replace loose file listing/grep checks with explicit tests for dist/cosmic_ray-${VERSION}-py3-none-any.whl, dist/cosmic_ray-${VERSION}.tar.gz, and assert that exactly two files exist in dist.

Testing

  • Locally executed the packaging commands and the new verification commands to confirm the wheel and sdist are produced and named for the prepared version, and the checks succeeded.
  • The repository's CI workflow file was updated only for the release job verification and no unit test suite changes were made.

Codex Task

The VCS build can derive a development version even after the workflow computes the intended release version. PyPI then receives artifacts whose version does not match the release metadata.\n\nPass the prepared version to setuptools-scm during the build and require both distribution filenames to match it before publishing. Restore setup-uv's latest selector because it was unrelated to the package version failure.
@abingham
abingham merged commit caf9a31 into master Aug 9, 2026
5 checks passed
@abingham
abingham deleted the codex/investigate-failed-release-ci-job branch August 9, 2026 14:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant