fix(release): bump pypi-publish action to v1.14.2; fix empty release-notes excerpt - #412
Conversation
![Mikhail [azalio] Petrov](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
…notes excerpt Two release-pipeline defects found while releasing 3.25.0: 1. pypa/gh-action-pypi-publish@v1.13.0 bundles an older twine that rejects Metadata-Version 2.5 wheels (InvalidDistribution). The repo's own twine-check step was already fixed in #411, but the action runs its own check internally. v1.14.2 ships twine v7 with core-metadata 2.5 support (upstream #416). Applied in release.yml and test-pypi.yml. 2. The GitHub Release changelog excerpt was always empty: the two-address awk range /^## \[VERSION\]/,/^## \[/ collapses to a single line because the version heading matches both patterns, so every release body fell back to 'See CHANGELOG.md for details.' (verified on v3.24.1). Replaced with a flag state machine in release.yml, the release-checklist issue template, and the map-release skill (.jinja source + rendered trees).
|
Warning Review limit reached
Next review available in: 25 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Summary
Release run 31590633496 for v3.25.0 failed at Publish to PyPI using OIDC; nothing was published (verified: 3.25.0 absent on PyPI, no GitHub Release).
Root causes
pypa/gh-action-pypi-publish@v1.13.0bundles an older twine that rejects Metadata-Version 2.5 wheels — the action runs its own internaltwine check, so the fix(ci): allow packaging>=26 so twine check accepts Metadata-Version 2.5 #411 fix to the repo's check step didn't reach it. Upstream v1.14.2 ships twine v7 with core-metadata 2.5 support (upstream PR Update twine to v7 pypa/gh-action-pypi-publish#416).awk "/^## \[VERSION\]/,/^## \[/"collapses to one line (the heading matches both patterns) → every GitHub Release body was the stub "See CHANGELOG.md for details." (verified on v3.24.1). Fixed with a flag state machine inrelease.yml, the release-checklist issue template, and the map-release skill (jinja source + rendered trees;make check-rendergreen).Verification
make check-render✅,pytest tests/test_template_render.py tests/test_skills.py→ 359 passed.Release plan after merge
v3.25.0 tag will be moved to the merged HEAD and re-pushed (nothing was published, so the version number is unused).
🤖 Generated with Claude Code