Skip to content

Use TestPyPI API token auth instead of username/password.#392

Merged
RishabhJain2018 merged 1 commit into
masterfrom
ci/testpypi-api-token
Jun 14, 2026
Merged

Use TestPyPI API token auth instead of username/password.#392
RishabhJain2018 merged 1 commit into
masterfrom
ci/testpypi-api-token

Conversation

@RishabhJain2018

@RishabhJain2018 RishabhJain2018 commented Jun 14, 2026

Copy link
Copy Markdown
Member

Authenticate TestPyPI uploads with token and TEST_PYPI_API_TOKEN, matching the production PyPI publish flow.

Summary by CodeRabbit

  • Documentation

    • Updated CI/CD documentation to reflect TestPyPI authentication configuration.
  • Chores

    • Updated TestPyPI publishing workflow to use API token authentication.

Authenticate TestPyPI uploads with __token__ and TEST_PYPI_API_TOKEN,
matching the production PyPI publish flow.
@coderabbitai

coderabbitai Bot commented Jun 14, 2026

Copy link
Copy Markdown

Review Change Stack

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ea1f4d57-e767-4b84-848e-d55184476896

📥 Commits

Reviewing files that changed from the base of the PR and between 9d7675d and 3792374.

📒 Files selected for processing (2)
  • .github/CI_CD.md
  • .github/workflows/ci-cd.yml

📝 Walkthrough

Walkthrough

The publish_to_testpypi workflow step is updated to use token-based authentication: TWINE_USERNAME is hardcoded to __token__ and TWINE_PASSWORD is sourced from a new TEST_PYPI_API_TOKEN secret, replacing the previous TEST_PYPI_USERNAME/TEST_PYPI_PASSWORD pair. The CI/CD documentation table is updated to match.

Changes

TestPyPI Token Authentication

Layer / File(s) Summary
Token-based TestPyPI auth in workflow and docs
.github/workflows/ci-cd.yml, .github/CI_CD.md
publish_to_testpypi step sets TWINE_USERNAME to __token__ and TWINE_PASSWORD from secrets.TEST_PYPI_API_TOKEN; the required secrets table in the docs is updated from two entries (TEST_PYPI_USERNAME, TEST_PYPI_PASSWORD) to one (TEST_PYPI_API_TOKEN).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • Cloud-CV/evalai-cli#391: Directly related — this PR updates the same publish_to_testpypi step in .github/workflows/ci-cd.yml that PR #391 introduced during the GitHub Actions CI/CD migration.

Poem

🐇 A token, a token, one secret to share,
No username, no password — just one credential there!
__token__ the username, the API key the key,
TestPyPI now shines with simplicity!
hippity-hop, the secrets are clean! 🎉

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ci/testpypi-api-token

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 and usage tips.

@RishabhJain2018 RishabhJain2018 merged commit 6030779 into master Jun 14, 2026
2 of 3 checks passed
@RishabhJain2018 RishabhJain2018 deleted the ci/testpypi-api-token branch June 14, 2026 22:00
@codecov

codecov Bot commented Jun 14, 2026

Copy link
Copy Markdown

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

Thanks for integrating Codecov - We've got you covered ☂️

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.

1 participant