ci: fix PyPI publishing process, enforce mypy types#20
ci: fix PyPI publishing process, enforce mypy types#20cademirch merged 6 commits intosnakemake:mainfrom
Conversation
|
Important Review skippedReview was skipped as selected files did not have any reviewable changes. 💤 Files selected but had no reviewable changes (1)
You can disable this status message by setting the 📝 WalkthroughWalkthroughThe GitHub Actions workflow file has been revised to update the build and release process. The job formerly known as Changes
Possibly related PRs
Suggested reviewers
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
.github/workflows/release-please.yml (2)
30-35: Pixi Installation Step
The Pixi installation is implemented withprefix-dev/setup-pixi@v0.8.3, specifying both thepixi-version: v0.42.1and theenvironments: publishparameter. This step appears correct, but please double-check that the parameter key (environments) exactly matches the expected input for the Pixi action.
42-42: File Ending Newline
Static analysis has flagged that there is no newline character at the end of the file. Please add a newline at the end to comply with YAML linting rules and improve file formatting.🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 42-42: no new line character at the end of file
(new-line-at-end-of-file)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (2)
pixi.lockis excluded by!**/*.lockpyproject.tomlis excluded by!pyproject.toml
📒 Files selected for processing (1)
.github/workflows/release-please.yml(1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
.github/workflows/release-please.yml
[error] 42-42: no new line character at the end of file
(new-line-at-end-of-file)
🔇 Additional comments (4)
.github/workflows/release-please.yml (4)
19-27: New Job Introduction: Publish-PyPI Job
The addition of thepublish-pypijob is well-structured. It correctly depends on therelease-pleasejob and sets appropriate permissions and environment. Verify that the conditionalif: ${{ needs.release-please.outputs.release_created }}reliably triggers the job only when a release is actually created.
28-29: Checkout Step in Publish-PyPI Job
The checkout step usingactions/checkout@v4is standard and properly positioned as the first step in the new job.
36-39: Build Distribution and Check Build Step
The build step runs the commandpixi run --environment publish check-buildto build both source and wheel distributions, which is critical for ensuring package integrity before publishing. The accompanying comment clarifies the intent, and the implementation adheres to the new workflow requirements.
41-42: Publish Distribution to PyPI Step
The use ofpypa/gh-action-pypi-publish@release/v1to publish the distribution to PyPI is a standard approach and is appropriately placed after the build validation step.🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 42-42: no new line character at the end of file
(new-line-at-end-of-file)
cademirch
left a comment
There was a problem hiding this comment.
Lgtm. Thanks for tackling this.
Introduce a new publish environment in
pyproject.tomland update the release workflow to fix the PyPI publishing process.Summary by CodeRabbit
Chores
Documentation