Skip to content

ci(publish): gate release on the locked env; PyPI trusted publishing - #9

Merged
SaulBuilds merged 1 commit into
mainfrom
ci/publish-locked-env
Sep 25, 2026
Merged

SaulBuilds merged 1 commit into
mainfrom
ci/publish-locked-env

Conversation

@SaulBuilds

Copy link
Copy Markdown
Contributor

The release workflow's test job used a stale install and a --cov flag without the coverage plugin, so the v0.6.2 release run failed before build. Nothing was uploaded.

  • The test job now runs the same frozen uv.lock checks as CI's locked-env job: ruff, mypy and pytest on Python 3.11.
  • Publishing uses PyPI Trusted Publishing (OIDC). The unused PYPI_API_TOKEN input is removed.

No package code changes.

🤖 Generated with Claude Code

https://claude.ai/code/session_012cD3fDq5vhh2YWZPU2SV6H

The publish workflow's test job used a stale install (pip install -e .[dev]
plus a --cov flag with no coverage plugin), so a release failed before build.
It now runs the same frozen uv.lock checks as CI's locked-env job. Publishing
uses PyPI Trusted Publishing (OIDC) with no API token.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012cD3fDq5vhh2YWZPU2SV6H
@SaulBuilds
SaulBuilds merged commit 6f4084c into main Sep 25, 2026
13 checks passed
@SaulBuilds
SaulBuilds deleted the ci/publish-locked-env branch September 25, 2026 23:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants