auto-publish unstable packages to NPM #625
Merged
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.
As there's no convenient way to point NPM directly at a monorepo, and even if you could the package does have a required build step.
The build step for v2 addons was a deliberate design choice, because in the normal case apps can have much faster builds if all their addons are already prebuilt before publishing. But it does make the case of using unreleased code more manual.
This PR adds workflow to automatically publish alpha releases to NPM for every commit to the master branch.
This is inspired by setup in https://github.com/ember-animation/ember-animated/blob/master/.github/workflows/publish-unstable.yml
@lukemelia would you be open doing this? If yes - could you please add npm token as
NODE_AUTH_TOKEN
secret to the repository config?