Skip to content

fix(release): remove obsolete NPM_RELEASE_ENABLED gate - #52

Merged
bhouston merged 1 commit into
mainfrom
fix/51-remove-npm-release-gate
Sep 18, 2026
Merged

bhouston merged 1 commit into
mainfrom
fix/51-remove-npm-release-gate

Conversation

@bhouston

Copy link
Copy Markdown
Owner

Summary

  • Removes the if: vars.NPM_RELEASE_ENABLED == 'true' gate (and its comment) from the release job in .github/workflows/release.yml, since npm trusted publishing is now fully configured for hdrify, hdrify-cli, and hdrify-react, and the release baseline tag exists.
  • Updates RELEASING.md to remove references to setting the now-obsolete NPM_RELEASE_ENABLED Actions variable.
  • The guard job (dispatch-against-main check) and baseline-tag mechanics are untouched.

Closes #51

Validation

  • git diff reviewed: only the gate lines and the two NPM_RELEASE_ENABLED mentions in RELEASING.md changed.
  • CI will run the reusable checks workflow on this PR.

npm trusted publishing is fully configured for hdrify, hdrify-cli, and
hdrify-react, and the release baseline tag exists, so the manual
activation gate on the release job is no longer needed. This aligns
the release workflow with sibling repos that don't carry this gate.

Refs #51
@bhouston
bhouston merged commit b90c2cf into main Sep 18, 2026
2 checks passed
@bhouston
bhouston deleted the fix/51-remove-npm-release-gate branch September 18, 2026 19:58
@codecov-commenter

Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

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.

Remove obsolete NPM_RELEASE_ENABLED gate from release workflow

2 participants