As a Release Candidate, publish steps are slightly different. Main difference: solely publishing to NPM, but not to master (let alone to Kitchen Sink).
[ ] Create an issue for everything else, e.g. new component, updated component, new variation, docs addition/edits, etc. Generally culled from this fsa-style's Release Notes.
[ ] Alternately: log fsa-design-systemIssue noting need to log issues related to this release.
[ ] Be honest, did you really author Release Notes?. If not, do it now, or at least log a P1 issue to do so soon.
As a Release Candidate, publish steps are slightly different. Main difference: solely publishing to NPM, but not to
master(let alone to Kitchen Sink).scratch.html)package.jsonCommit those changes and pushdevelopTest, test, test.Merge tomaster(fromdevelop)Switch tomasterPrune branches (local and remote)gruntto test build and validate.PushmasterValidate at https://github.com/USDA-FSA/fsa-style/commits/mastermasterrelease/2.6.0to2.6.0-RC1git push origin [tag_name])npm run deployDeploys dist to gh-pagesMay need to use GitBash or GitShell to perform due to association with ssh key.Validate at http://usda-fsa.github.io/fsa-style/ (might take more than a handful of minutes).grunt compress- creates a versioned ZIP of dist in/published/(which is not committed)/published/)fsa-styleIssue to author Release Notes.npm publishCreate issue to soft-launch in fsa-design-system e.g. https://github.com/USDA-FSA/fsa-design-system/issues/322fsa-style@x.x.xreferences (most especially on Getting Started). e.g. https://github.com/USDA-FSA/fsa-design-system/issues/243fsa-styledependency to this new version. e.g. https://github.com/USDA-FSA/fsa-design-system/issues/244fsa-style's Release Notes.fsa-design-systemIssue noting need to log issues related to this release.