Skip to content

chore: update shared npm release workflow - #31

Merged
jan-kubica merged 1 commit into
mainfrom
chore/update-npm-release-pin
Aug 26, 2026
Merged

chore: update shared npm release workflow#31
jan-kubica merged 1 commit into
mainfrom
chore/update-npm-release-pin

Conversation

@jan-kubica

@jan-kubica jan-kubica commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Update the shared npm release workflow pin to immutable commit dd6e8fa51339814159486cd92b5ae3a051eb15d2, which includes five-minute npm registry visibility polling before completing a release. Caller inputs and release semantics stay unchanged.

CC on behalf of jan-kubica

Summary by CodeRabbit

  • Chores
    • Updated the automated release workflow to use a newer workflow version.
    • Release workflow inputs and permissions remain unchanged.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for security reviews. Please try again later.

@coderabbitai

coderabbitai Bot commented Aug 26, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 92256bc7-f407-4b0d-9aa8-800e40d038f6

📥 Commits

Reviewing files that changed from the base of the PR and between 97b7efc and 4db8383.

📒 Files selected for processing (1)
  • .github/workflows/publish.yml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The release job now references commit dd6e8fa51339814159486cd92b5ae3a051eb15d2 of the reusable npm release workflow. Inputs and permissions remain unchanged.

Changes

Release workflow

Layer / File(s) Summary
Update reusable workflow reference
.github/workflows/publish.yml
The release job uses the updated reusable workflow commit.

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

Merge Risk: ⚪ Minimal · up to 4db83

This localized workflow pin update preserves the existing release inputs and semantics while adopting the specified registry-visibility polling behavior; no actionable merge-blocking risk remains beyond normal checks and review.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 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 shared npm release workflow reference.
Docstring Coverage ✅ Passed 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 ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed 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)
  • Create PR with unit tests
  • Commit unit tests in branch chore/update-npm-release-pin

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.

@jan-kubica
jan-kubica merged commit 8630e29 into main Aug 26, 2026
6 checks passed
@jan-kubica
jan-kubica deleted the chore/update-npm-release-pin branch August 26, 2026 13:35
@github-actions github-actions Bot locked and limited conversation to collaborators Aug 26, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant