Add support for publishing to npm from GitHub#26
Merged
skirtles-code merged 1 commit intomainfrom Apr 20, 2026
Merged
Conversation
commit: |
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
1 participant
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.
The main addition in this PR is publishing to npm from GitHub with trusted publishing. The project itself already uses trusted publishing since #24. This is now supported for the projects it creates.
While updating the docs it became apparent that the other workflows are a little more restrictive than they need to be, only running for changes/PRs targeting the
mainbranch and not running on forks even in cases where that would be useful. That has also been adjusted.pages.yml.ejshas also been synced withpages.yml, so that it no longer runs for pushes tomain. It can still be run manually and is also triggered by publishing to npm viapublish.yml. This is to ensure that the docs don't get ahead of released changes.