Updated package.json with pre-/post-release tasks to make publishing easier; also added docs creation and adding Prettier/doc updates to a commit if they make changes so you don't have to make another commit and squash.
In the publishing flow, added prerelease and postrelease tasks to package.json, so it goes:
Dev continues as normal on a feature branch (initial-release in our case)
PR to move the feature branch to master, review, merge
Locally do npm run release, which first kicks off the prerelease tasks
a. Locally checks out master
b. Pulls the latest code
c. Installs/updates dependencies
d. Runs a validation check - linting, testing, and checks for formatting errors
If those pass, it runs standard-release to bump the version and update the change log, and creates a tag on the branch and a new chore commit for release
On completion, triggers postrelease tasks
a. Pushes the tagged branch back to master
b. Publishes to NPM
When we roll with Actions, we can automate this to trigger simply from the commit to master
For now, though, all it takes to update/tag/publish is a single command locally.
Updated package.json with pre-/post-release tasks to make publishing easier; also added
docscreation and adding Prettier/doc updates to a commit if they make changes so you don't have to make another commit and squash.In the publishing flow, added
prereleaseandpostreleasetasks topackage.json, so it goes:initial-releasein our case)npm run release, which first kicks off the prerelease tasks a. Locally checks outmasterb. Pulls the latest code c. Installs/updates dependencies d. Runs avalidationcheck - linting, testing, and checks for formatting errorsstandard-releaseto bump the version and update the change log, and creates a tag on the branch and a new chore commit for releaseWhen we roll with Actions, we can automate this to trigger simply from the commit to master
For now, though, all it takes to update/tag/publish is a single command locally.
re #50