fix: release using PEP 517

[m1so]

Summary by CodeRabbit

• Chores
  • Updated build and packaging infrastructure to use modern Python build standards.

---

Note: This release contains internal build process improvements with no impact to end-user functionality.

[coderabbitai]

📝 Walkthrough

Walkthrough

The release workflow in .github/workflows/release.yml has been updated to shift from setuptools-based packaging to PEP 517/518 build standards. The caching key now targets pyproject.toml instead of setup.py. Build dependencies have been consolidated—replacing setuptools and wheel with the build package—and the explicit wheel and source distribution commands are now unified into a single python -m build invocation.

Possibly related PRs

• ci: Publish to pypi #2: Modifies the same release workflow with related adjustments to packaging and environment variables.

Pre-merge checks

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The PR title "fix: release using PEP 517" directly describes the main change in the changeset. The release workflow is being updated to transition from setuptools-based packaging to PEP 517/518 build tooling, which is exactly what the title conveys. The title is specific, concise, and avoids vague language—it clearly indicates the primary purpose of the changes.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 08554e6 and c12c4a4.

📒 Files selected for processing (1)

• .github/workflows/release.yml (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (9)

• GitHub Check: Win Py3.9
• GitHub Check: Win Py3.11
• GitHub Check: Win Py3.10
• GitHub Check: Mac Py3.9
• GitHub Check: Mac Py3.10
• GitHub Check: Linux Py3.11
• GitHub Check: Linux Py3.10
• GitHub Check: Linux Py3.9
• GitHub Check: Mac Py3.11

🔇 Additional comments (3)

.github/workflows/release.yml (3)

40-40: Build dependencies correctly consolidated to build package.

Replacing explicit setuptools wheel with build is the proper PEP 517 approach.

---

43-43: Project properly configured for PEP 517 builds.

Verified: pyproject.toml contains [build-system] with build-backend = "setuptools.build_meta" and required dependencies. The python -m build command will correctly orchestrate the build per PEP 517.

---

29-29: Cache key change is valid.

pyproject.toml exists and declares build-backend = "setuptools.build_meta", confirming PEP 517 setup.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}