ci: publish Node SDK from GitHub releases - #27
Merged
Conversation
Bjornftw
approved these changes
Sep 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A push to main currently creates and publishes a release through semantic-release. This change publishes to npm only when a GitHub release is published. The workflow checks out the release tag and updates package.json and package-lock.json before the checks and build. Stable releases use latest; prereleases use next.
Remove semantic-release and its dependencies. After a successful npm upload, call the Discord workflow and open a pull request for stable version and changelog updates. Skip Discord if the webhook secret is absent.
Validation on the PR commit: clean dependency install, lint, type checks, all 42 tests, build, package preview, and actionlint passed. Eleven release-tag checks also passed, including invalid tags and prerelease routing. No package was published.
Publication uses the existing release.yaml workflow name for npm trusted publishing. The repository must permit GitHub Actions to create pull requests for version and changelog updates.