# Tailwind CSS v1.9.3 — Release & Upgrade Intelligence
- **Product:** Tailwind CSS (https://tailwindcss.com)
- **Version:** v1.9.3
- **Released:** Oct 16, 2020
- **Impact Score:** 7/10
- **Breaking Changes:** Source flagged
- **Canonical Analysis:** https://changelogs.us/tailwind/updates/v1.9.3/

## Executive Summary (TL;DR)
Tailwind CSS v1.9.3. Source highlight: Fix issue where `tailwindcss init --full` scaffolded a corrupt config file (https://github.com/tailwindlabs/tailwindcss/issues/2556)

## Breaking Changes & Deprecations
- - Remove console warnings about upcoming breaking changes (see note below)
- I've opted to remove the console notices about upcoming breaking changes (that encouraged users to opt-in to future features using the `future` option in their config file.)
- While I had good intentions for this approach originally, I'm realizing now that it just ends up creating more confusion and a sloppier documentation story. Any breaking changes can't really be documented easily because the documentation needs to show the _stable_ version of any given feature, since we can't assume someone has opted in to the new stuff.
- For this reason I've decided to stop warning about the upcoming breaking changes so that we don't force users to opt-in to an essentially undocumented version of the framework. Instead we will continue to maintain the "upcoming changes" page in the docs, and continue to ship new ideas behind flags for people to test but without the nudge to upgrade. Folks who are comfortable opting-in to the new stuff early can do so, and folks that aren't can comfortably keep using things the way they are (along with complete documentation) and upgrade to the next version all at once, like people have done tr
- I will always strive to make breaking changes as painless and minimal as possible, so spending an hour to do the upgrade in one sitting is never going to be too bad. I highly value backwards compatibility and will never make needlessly breaking changes. An improvement is only worth making if it improves things enough to make up for the upgrade cost, and that's usually pretty rare. For example `lh-5` might be a nicer class name than `leading-5` but it is absolutely _not_ worth breaking everyone's muscle memory and forcing them to replace hundreds of instances of classes in their projects. We'll

## Bug Fixes
- Fix issue where `tailwindcss init --full` scaffolded a corrupt config file (https://github.com/tailwindlabs/tailwindcss/issues/2556)

## Upgrade Command
```bash
npm install --save-exact tailwindcss@1.9.3
```