Publishing new version

For fsa-style issues assigned to [Milestone x.x.x]

• Prune unneeded files (e.g. scratch.html)
• Bump semver number in package.json
• Edit references to version number:
  • In title of index.html
  • README.md
• Commit those changes and push develop
  • Test, test, test.
• Merge to master (from develop)
  • Switch to master
  • Prune branches (local and remote)
• Push master
• One last grunt to test build and validate.
• Create tag from master to x.x.x
  • Push new tag to origin (git push origin [tag_name])
• npm run deploy Deploys dist to gh-pages
  • May need to use GitBash or GitShell to perform due to association with ssh key.
    • https://gist.github.com/adamjohnson/5682757
    • https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account
  • 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)
• Draft a new Release
  • Attach ZIP (from /published/)
  • Tag and title are identical, e.g. "0.2.7" (note, not "v0.2.7")
  • Add Release Notes. Example: Release 2.2.0.
    • Alternately: log fsa-style Issue to author Release Notes.
  • Publish Release
• npm publish
  • Validate at https://www.npmjs.com/package/fsa-style
• fsa-design-system issues to log
  • Update [email protected] references (most especially on Getting Started). e.g. https://github.com/USDA-FSA/fsa-design-system/issues/243
  • Update fsa-style dependency to this new version. e.g. https://github.com/USDA-FSA/fsa-design-system/issues/244
  • 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-system Issue 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.