Release 2.7.7

[bignamehere]

Steps

• [x] Prune unneeded files (e.g. scratch.html)
• [x] Bump semver number in package.json
• [x] Edit references to version number:
  • [x] In title of index.html
  • [x] README.md
• [x] Ensure all features are on branch release/x.x.x
• [x] Merge in
  • [x] Switch to master
  • [x] Merge to master (from release/x.x.x)
• [x] One last grunt to test build and validate.
• [x] Prune branches (local and remote)
• [x] Push master
  • [x] Validate at https://github.com/USDA-FSA/fsa-style/commits/master
• [x] Create tag from master to x.x.x
  • [x] Example:git tag -a [version] -m "version [version]" and git show [version] to check
  • [x] Push new tag to origin (git push origin [tag_name])
  • [x] Validate at https://github.com/USDA-FSA/fsa-style/tags
• [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://gist.github.com/adamjohnson/5682757
    • 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)
• [x] 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")
  • [x] 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?activeTab=versions
• [x] Create issue to soft-launch in fsa-design-system e.g. https://github.com/USDA-FSA/fsa-design-system/issues/532
• [ ] fsa-design-system issues to log
  • [ ] Update fsa-style@x.x.x 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
  • [x] 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.
    • [x] Alternately: log fsa-design-system Issue noting need to log issues related to this release.
• [x] Be honest, did you really author Release Notes?. If not, do it now, or at least log a P1 issue to do so soon.
• [x] Submit BLDCON ticket in Jira (https://jira.fpac.usda.gov/projects/BLDCON/issues/BLDCON-698?filter=allopenissues) to procure newest fsa-style version to Nexus - ping Adi Rosenblum and/or Aaron Diffenderfer in Teams to give them the ticket number Example: https://jira.fpac.usda.gov/browse/BLDCON-2576