Minor Release Tracking PR 10.9.0

[emplums]

Primer Minor Release

Tracking Issue for next minor release: 📦 10.9.0
Approximate release date: 📆 10/19/18

🚀 New features

• Responsive border utilities in Add responsive border utilities #552 via Simplify responsive utilities with $responsive-variants #545
• Counters get visibility: hidden when empty (:empty) Hiding .Counter component when it's empty. #586

🐛 Bug fixes

• Add !important to [hidden] Add !important to [hidden] #557 /cc @muan

💅 Housekeeping

• Warn about planned deprecations in Major release 11.0.0 #498 @shawnbot
• Replace a bunch of custom code with code-blocks
• Remove zero-width negative margin utilities (*-n0) in Simplify responsive utilities with $responsive-variants #545
• Add stories.js to new module template Add default stories.js to module template #584

📝 Documentation

• Remove invalid button class references (btn-outline-blue and btn-secondary) from docs Remove invalid button classes #580

---

Ship checklist

• Update CHANGELOG
• Run version bump
• Create a git tag
• Create github release
• Open PR for next release Release 10.10.0 #588
• Update primer.github.io (not necessary because we redirect to primer.style)
• Update github/github
• Update the style guide https://github.com/github/styleguide/pull/261

/cc @primer/ds-core

[shawnbot]

Let's do this.

[shawnbot]

FYI, the commits after 83cc7e8 are me trying to figure out why our release candidate script failed to publish the (AFAICT correct) release candidate version of primer-blankslate@1.4.10-rc.1. That shouldn't be a problem, since:

% npm view primer-blankslate@rc .version
1.4.10-rc.0

🤔

[shawnbot]

Well, I'm kinda stuck for the moment on this error:

npm notice 📦  primer-marketing@6.3.0-rc.1
npm notice === Tarball Contents === 
npm ERR! publish Failed PUT 403

I can't actually tell if the 403 is happening when attempting to publish primer-marketing@6.3.0-rc.1 because it looks like the output for all of our publish commands is interleaved. That shouldn't be the problem, though, because, again:

% npm view primer-marketing@rc .version
6.3.0-rc.0
% npm view primer-marketing@6.3.0-rc.1
(nada)

[shawnbot]

🚨 @jonrohan and I discussed this in Slack and agreed to disable the release candidate publishing to get this release out. I'll re-enable it in #588 by removing the --dry-run flag from .travis.yml.