USWDS web-components: Configure publication to NPM#62
USWDS web-components: Configure publication to NPM#62heymatthenry wants to merge 3 commits intodevelopfrom
Conversation
mejiaj
left a comment
mejiaj
left a comment
There was a problem hiding this comment.
@heymatthenry looking forward to seeing this included in this repo and others, thank you!
Minor comment on what triggers the release. Our current release process includes GitHub releases and then publishing to NPM. The nice thing about it is that we can thoroughly document and provide a good changelog.
Open to other ideas and iterating on this if we simply want to test the action.
| node-version: '20.x' | ||
| registry-url: 'https://registry.npmjs.org' | ||
| - run: npm ci | ||
| - run: npm publish --provenance --access public --tag develop |
There was a problem hiding this comment.
praise: Provenance flag is a great idea!
| on: | ||
| push: | ||
| branches: | ||
| - develop |
There was a problem hiding this comment.
question: Should this be on [published] or main?
Going off of example workflow guidance:
name: Publish package to GitHub Packages
on:
release:
types: [published]
…
mejiaj
left a comment
mejiaj
left a comment
There was a problem hiding this comment.
Approving because we'll also be tagging and releasing on main (like we currently do in USWDS).
2 participants
Summary
Configured package for publication and created a workflow to automatically publish to
@uswds/web-components@developon pushes todevelop