Skip to content

ci: require opt-in for manual npm publish#14

Merged
mertushka merged 1 commit into
mainfrom
ci/manual-release-publish-opt-in
Jun 14, 2026
Merged

ci: require opt-in for manual npm publish#14
mertushka merged 1 commit into
mainfrom
ci/manual-release-publish-opt-in

Conversation

@mertushka

Copy link
Copy Markdown
Owner

Purpose

Prevent a routine manual Release workflow dispatch from publishing to npm or recreating a prerelease distribution tag unintentionally.

Changes

  • default manual publish_npm input to false
  • clarify that npm_tag applies only when npm publication is explicitly enabled
  • document asset-only defaults and the explicit manual publication procedure

Impact

  • Automatic GitHub Release publication: unchanged
  • Manual asset rebuilds: safer default; they still build and replace release assets
  • Manual npm publication: still supported through explicit publish_npm opt-in
  • Public/runtime behavior: none
  • Native addon: none
  • WPT/conformance: none
  • Browser interoperability: none

Validation

  • npm run check
  • git diff --check
  • actionlint 1.7.12 across all workflows using the previously checksum-verified upstream Windows binary

@mertushka mertushka marked this pull request as ready for review June 14, 2026 00:52
@mertushka mertushka merged commit 243a68e into main Jun 14, 2026
19 checks passed
@mertushka mertushka deleted the ci/manual-release-publish-opt-in branch June 14, 2026 00:52
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