Skip to content

Conversation

@timosachsenberg
Copy link
Collaborator

@timosachsenberg timosachsenberg commented Dec 31, 2025

  • Update pypa/gh-action-pypi-publish from @master to @release/v1
  • Remove deprecated 'user' parameter (defaults to token)
  • Fix parameter name: packages_dir -> packages-dir
  • Update stefanzweifel/git-auto-commit-action from v4.15.2 to v5

Summary by CodeRabbit

  • Chores
    • Updated GitHub Actions workflow to use newer versions of deployment and automation tools.

✏️ Tip: You can customize this high-level summary in your review settings.

- Update pypa/gh-action-pypi-publish from @master to @release/v1
- Remove deprecated 'user' parameter (defaults to __token__)
- Fix parameter name: packages_dir -> packages-dir
- Update stefanzweifel/git-auto-commit-action from v4.15.2 to v5
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 31, 2025

📝 Walkthrough

Walkthrough

Updated GitHub Actions workflow file to use newer versions of public actions: PyPI publish action moved to release/v1 branch with renamed input parameters, and git-auto-commit-action incremented to v5. Removed deprecated user input from the publish step.

Changes

Cohort / File(s) Summary
GitHub Actions Workflow Configuration
\.github/workflows/release-autowrap\.yaml
Updated PyPI publish action from master to release/v1; renamed packages_dirpackages-dir; removed user input parameter; upgraded git-auto-commit-action from v4.15.2 → v5

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A workflow renewed, through actions anew,
Version bumps and renames, the release runs true,
Git commits dancing, PyPI's release takes flight,
Our automation updated, automation feels right!

Pre-merge checks

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: updating the PyPI publish action to fix broken publishing, which directly matches the PR's primary objective.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 22ae49b and d0ced70.

📒 Files selected for processing (1)
  • .github/workflows/release-autowrap.yaml
⏰ 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). (8)
  • GitHub Check: test (==3.2.0, 3.13)
  • GitHub Check: test (==3.1.0, 3.10)
  • GitHub Check: test (==3.2.0, 3.12)
  • GitHub Check: test (==3.2.0, 3.10)
  • GitHub Check: test (==3.1.0, 3.13)
  • GitHub Check: test (==3.2.0, 3.11)
  • GitHub Check: test (==3.1.0, 3.12)
  • GitHub Check: test (==3.1.0, 3.11)
🔇 Additional comments (2)
.github/workflows/release-autowrap.yaml (2)

97-97: No compatibility issues with v5 upgrade.

The parameters commit_message and file_pattern remain unchanged and fully supported in v5. The v5 action.yml confirms both inputs are present with identical behavior to v4.15.2, and no breaking changes are documented in the release notes. The major version bump is safe to use.


56-59: Good migration to stable action version.

The updates are correct:

  • Moving from @master to @release/v1 follows the official recommendation (the master branch has been sunset).
  • The parameter rename from packages_dir to packages-dir aligns with the documented v1 API.
  • Removing the user parameter is appropriate; it defaults to __token__ for PyPI token authentication.

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.

@timosachsenberg timosachsenberg merged commit 0410f82 into master Dec 31, 2025
10 of 11 checks passed
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.

3 participants