Publish 2.4.0 Production Release

[francisrupert]

For fsa-style issues assigned to Milestone 2.4.0

• [x] Bump semver number in package.json
• [x] Edit references to version number:
  • [x] In title of index.html
  • [x] README.md
• [x] Commit those changes and push develop
  • [x] Test, test, test.
• [x] Merge to master (from develop)
  • [x] Switch to master
  • [x] Prune branches (local and remote)
• [x] Push master
• [x] One last grunt to test build and validate.
• [x] Create tag from master to x.x.x
  • [x] Push new tag to origin (git push origin [tag_name])
• [x] npm run deploy Deploys dist to gh-pages
  • [x] May need to use GitBash or GitShell to perform due to association with ssh key.
    • https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account
  • [x] Validate at http://usda-fsa.github.io/fsa-style/ (might take more than a handful of minutes).
• [x] grunt compress - creates a versioned ZIP of dist in /published/ (which is not committed)
• [ ] Draft a new Release
  • [x] Attach ZIP (from /published/)
  • [x] Tag and title are identical, e.g. "0.2.7" (note, not "v0.2.7")
  • [ ] Add Release Notes. Example: Release 2.2.0.
    • [x] Alternately: log fsa-style Issue to author Release Notes.
  • [x] Publish Release
• [x] npm publish
  • [x] Validate at https://www.npmjs.com/package/fsa-style
• [ ] fsa-design-system issues to log
  • [x] Update fsa-style@x.x.x references (most especially on Getting Started). e.g. https://github.com/USDA-FSA/fsa-design-system/issues/243
  • [x] 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.
• [ ] Be honest, did you really author Release Notes?. If not, do it now, or at least log a P1 issue to do so soon.