Skip to content

ci: Use goreleaser-npm-publisher-action v1.6.0 - #104

Open
khvn26 wants to merge 5 commits into
mainfrom
ci/goreleaser-npm-publisher-action
Open

ci: Use goreleaser-npm-publisher-action v1.6.0#104
khvn26 wants to merge 5 commits into
mainfrom
ci/goreleaser-npm-publisher-action

Conversation

@khvn26

@khvn26 khvn26 commented Aug 22, 2026

Copy link
Copy Markdown
Member

goreleaser-npm-publisher-action v1.6.0 now supports inputs for differing package/repo/binary names, and including repository in package metadata.
In this PR, we migrate the release workflow from our fork to the new action version.

@coderabbitai

coderabbitai Bot commented Aug 22, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@khvn26, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 46 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 8ec794f9-2cb8-4f6b-8b9f-94de9d8c3238

📥 Commits

Reviewing files that changed from the base of the PR and between fc09551 and 252e2ee.

📒 Files selected for processing (2)
  • .github/workflows/release.yml
  • .goreleaser.yaml
📝 Walkthrough

Walkthrough

The release workflow replaces manual goreleaser-npm-publisher setup and CLI execution with the pinned goreleaser-npm-publisher-action. The workflow retains the package name, binary, scope, repository metadata, description, keywords, and published files.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: 🟡 Moderate · up to fc095

The release workflow currently formats package files incorrectly, which would omit README.md and LICENSE from generated packages. Merge should wait for this bounded release-artifact correctness issue to be fixed.


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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1


ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 37da0807-bdba-48a1-8b32-fb0e934e2d3e

📥 Commits

Reviewing files that changed from the base of the PR and between 2d55665 and fc09551.

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

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

Comment thread .github/workflows/release.yml Outdated
@khvn26
khvn26 force-pushed the ci/goreleaser-npm-publisher-action branch from 6f90e71 to 252e2ee Compare August 23, 2026 00:29
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.

1 participant