Skip to content

chore: migrate publish to pypa/gh-action-pypi-publish - #453

Merged
shenxianpeng merged 1 commit into
mainfrom
chore/scorecard-packaging
Jul 2, 2026
Merged

chore: migrate publish to pypa/gh-action-pypi-publish#453
shenxianpeng merged 1 commit into
mainfrom
chore/scorecard-packaging

Conversation

@shenxianpeng

Copy link
Copy Markdown
Member

Summary

Scorecard's Packaging check expects PyPI publishing to use the official pypa/gh-action-pypi-publish action. This PR migrates from raw twine upload commands to the action.

Changes

  • Publish to TestPyPI — replaced twine upload --repository testpypi with pypa/gh-action-pypi-publish using repository-url: https://test.pypi.org/legacy/
  • Publish to PyPI — replaced twine upload with pypa/gh-action-pypi-publish
  • Removed now-unnecessary TWINE_USERNAME env vars (the action handles auth via the password input)

Action pinned by SHA: 6733eb7d741f0b11ec6a39b58540dab7590f9b7d (v1.14.0).

Part of the Scorecard improvement effort (currently ? for Packaging → 10/10 after merge).

@shenxianpeng
shenxianpeng requested a review from a team as a code owner July 2, 2026 21:03
@netlify

netlify Bot commented Jul 2, 2026

Copy link
Copy Markdown

Deploy Preview for commit-check ready!

Name Link
🔨 Latest commit b3e0c79
🔍 Latest deploy log https://app.netlify.com/projects/commit-check/deploys/6a46d22fd2508f00082caaf7
😎 Deploy Preview https://deploy-preview-453--commit-check.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions github-actions Bot added the chore label Jul 2, 2026
@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@shenxianpeng, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 37 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a9d26db7-cea2-4312-b8e4-bf3b196940b4

📥 Commits

Reviewing files that changed from the base of the PR and between 5153477 and b3e0c79.

📒 Files selected for processing (1)
  • .github/workflows/publish-package.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/scorecard-packaging

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@sonarqubecloud

sonarqubecloud Bot commented Jul 2, 2026

Copy link
Copy Markdown

@shenxianpeng
shenxianpeng merged commit 230b4a4 into main Jul 2, 2026
12 checks passed
@shenxianpeng
shenxianpeng deleted the chore/scorecard-packaging branch July 2, 2026 21:05
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