-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
USWDS web-components: Configure publication to NPM #62
base: develop
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
praise: Provenance flag is a great idea!
on: | ||
push: | ||
branches: | ||
- develop |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: Should this be on [published]
or main
?
Going off of example workflow guidance:
name: Publish package to GitHub Packages
on:
release:
types: [published]
…
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving because we'll also be tagging and releasing on main
(like we currently do in USWDS).
Summary
Configured package for publication and created a workflow to automatically publish to
@uswds/web-components@develop
on pushes todevelop