Skip to content

fix(release): separate registry environments - #30

Merged
2chevskii merged 2 commits into
masterfrom
fix/registry-environments
Oct 4, 2026
Merged

2chevskii merged 2 commits into
masterfrom
fix/registry-environments

Conversation

@2chevskii

@2chevskii 2chevskii commented Oct 4, 2026 •

Copy link
Copy Markdown
Owner

Summary

Release publications need separate GitHub environments after the npm environment was renamed. Route npm staging through npmjs and GitHub Packages publication through the newly created github-packages environment, with each deployment linking to its registry package page. Run finish_release only when a GitHub release is published, removing the manual trigger and its inputs. Preserve independent matrix jobs, failed-job retries, staged npm publication, and existing PR/edge workflows; update the release guidance.

Validation

  • Build, ESLint, Prettier, and documentation build passed for the environment changes.
  • After removing the manual trigger, Prettier, actionlint, and git diff --check passed. Only actionlint's outdated ubuntu-26.04 runner-label check was excluded.
  • GitHub API confirmed that npmjs and github-packages exist and supplied the GitHub package page URL.
  • Release publication was not rerun.

@2chevskii
2chevskii merged commit cc21f60 into master Oct 4, 2026
5 checks passed
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