[renovate]

This PR contains the following updates:

Package	Type	Update	Change
pypa/gh-action-pypi-publish (changelog)	action	digest	dc37677 → 7245906

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

Summary by CodeRabbit

• Chores
  • Updated the pinned version of the automated PyPI publishing workflow action.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 9a71b25b-4b73-4b74-9361-bff18474aedd

📥 Commits

Reviewing files that changed from the base of the PR and between 84636ce and 7fcfdb9.

📒 Files selected for processing: 1

• .github/workflows/dist-test.yml

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

📝 Walkthrough

The deploy job in the distribution test workflow now uses a different pinned commit for pypa/gh-action-pypi-publish. The action remains on release/v1.

Changes: PyPI publish workflow

Layer / File(s)	Summary
Update publishing action pin .github/workflows/dist-test.yml	The deploy job now uses a different pinned commit for pypa/gh-action-pypi-publish. The action remains on release/v1.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Possibly related issues

• Issue 29 in nocarryr/python-dispatch tracks the same PyPI publishing action pin update.

Merge Risk: ⚪ Minimal · up to 7fcfd

The workflow pin matches the stated dependency update and presents no established merge-blocking risk.

Architecture risk: 🔵 Low · up to 7fcfd

The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency.

Changed systems: None identified.

Architecture concerns
No architecture-level concerns identified.

Review details

Before / after behavior

• observed — Modified behavior in .github/workflows/dist-test.yml: The deploy job now uses a different pinned commit for pypa/gh-action-pypi-publish; the action remains on release/v1.

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely identifies the update to the PyPI publishing action digest. It matches the main change.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{A rabbit checks the publish pin,
One commit shifts; the release stays.
The workflow hops along its path,
While release/v1 remains in place.
A quiet change, then carrots await.}

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

[coveralls]

coverage: 97.882%. remained the same — renovate/pypa-gh-action-pypi-publish-digest into master

[nocarryr]

Merge activity

• Oct 21, 12:42 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Oct 21, 12:42 AM UTC: @nocarryr merged this pull request with Graphite.