Skip to content

ci: use trusted publishing in release pipeline and trigger on tags#2060

Open
Yonghui-Lee wants to merge 1 commit into
fsspec:masterfrom
Yonghui-Lee:auto-release
Open

ci: use trusted publishing in release pipeline and trigger on tags#2060
Yonghui-Lee wants to merge 1 commit into
fsspec:masterfrom
Yonghui-Lee:auto-release

Conversation

@Yonghui-Lee

@Yonghui-Lee Yonghui-Lee commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

This PR makes release pipeline automatically run tests, build packages, create GitHub releases, and publish to PyPI upon a new tag push.

Close #1866

Key Changes

  1. CI Workflow (main.yaml):
    • Added the workflow_call trigger to allow the CI workflow to be called by the release workflow.
  2. Release Pipeline (pypipublish.yaml):
    • Trigger: Configured to trigger automatically on CalVer tag pushes (e.g., 2026.6.0).
    • CI Dependency: Added a ci job dependency to ensure all tests pass before any build or publish steps run.
    • Build: Uses the standard build module to generate source distributions and wheels.
    • GitHub Release: Automatically creates a GitHub release, generates release notes, and attaches the build artifacts.
    • PyPI Publish: Switched from legacy username/password secrets to Trusted Publishing (OIDC) using the official pypa/gh-action-pypi-publish action.

Setup Required

Trusted Publishing must be configured on PyPI.

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.

Switch to trusted publishing for package upload to PyPI in CI

1 participant