Continuous release with pkg.pr.new and esm.sh#8603
Continuous release with pkg.pr.new and esm.sh#8603limzykenneth wants to merge 13 commits intoprocessing:dev-2.0from
Conversation
|
@ksen0 @davepagurek This is done now and ready for review. The build and release are triggered on pull request event so each push update will run it, similar to the regular test CI; it will also run on push to Once built, the package will be published to pkg.pr.new in the same manner as publishing on NPM except it will be tagged with the specific commit rather than version number. Once publish, esm.sh will automatically pick it up and the relevant CDN link will be available. We should change the CI build run to require approval for all external contributors before merging this. Also involved is the comment bot @p5-bot, which will comment on PR like the above with relevant links ready to be used. "CDN link" is the link ready to be used in a script tag; "Published Packages" is the link that can be Please review the implementation to check I didn't miss any specific edge cases especially in terms of any unintended publishing. Once it all looks good we can squash and merge since the history here is mostly trial and error stuff from me. |
| branches: | ||
| - 'dev-2.0' | ||
| tags: | ||
| - '!**' |
There was a problem hiding this comment.
RC will get published on NPM so it is available through jsdelivr already
| run: npm run build | ||
|
|
||
| - name: Publish library | ||
| run: npx pkg-pr-new publish --no-template --json output.json --comment=off |
There was a problem hiding this comment.
also minor: pin pkg-pr-new version?
There was a problem hiding this comment.
pkg-pr-new is pin as a dev dependency in the repo and not through an action so should be fixed by package-lock.json
2 participants
Resolves #8570
Changes:
Add dev dependency and workflow required to enable continuous release. Still need to verify that the deployment and custom message is working as intended.