chore: v2.0.6

HISTORY.md

@@ -1,6 +1,11 @@
 Pure Change History
 ===================
 
+2.0.6 (2021-04-28)
+------------------
+
+* chore: update to cssmin@4
+
 2.0.5 (2021-01-20)
 ------------------
 

README.md

@@ -7,7 +7,6 @@ A set of small, responsive CSS modules that you can use in every web project.
 [http://purecss.io/][Pure]
 
 [![Build Status](http://img.shields.io/travis/pure-css/pure.svg?style=flat)][Build Status]
-[![Dependency Status](https://david-dm.org/pure-css/pure/dev-status.svg)](https://david-dm.org/pure-css/pure?type=dev)
 [![Gitter](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/pure-css/pure?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
 
 **This project is looking for maintainers to support and enhance Pure.css. If you are interested please [leave a comment](https://github.com/pure-css/pure/issues/692) in the Github issue.**
@@ -15,7 +14,6 @@ A set of small, responsive CSS modules that you can use in every web project.
 [Pure]: http://purecss.io/
 [Build Status]: https://travis-ci.com/pure-css/pure
 
-
 Features
 --------
 

RELEASE.md

@@ -14,44 +14,44 @@ This assumes the following repo's are cloned and `npm` installed:
 
 - [ ] **Update local Pure to latest from pure-css/pure#master**
 
-    ```
-    $ cd pure/
-    $ git pull upstream master
-    ```
+  ```bash
+  $ cd pure/
+  $ git pull upstream master
+  ```
 
 - [ ] **Build Pure via `grunt`**
 
-    ```
-    $ grunt
-    ```
+  ```bash
+  $ grunt
+  ```
 
 - [ ] **Review all src/.../tests/manual/ files in target environments, including:**
 
-    - [ ] IE 11
-    - [ ] Edge
-    - [ ] Chrome
-    - [ ] Firefox
-    - [ ] Safari
-    - [ ] iOS 10.x
-    - [ ] Android 4.x
-    - [ ] Android 5.x
+  - [ ] IE 11
+  - [ ] Edge
+  - [ ] Chrome
+  - [ ] Firefox
+  - [ ] Safari
+  - [ ] iOS 10.x
+  - [ ] Android 4.x
+  - [ ] Android 5.x
 
 - [ ] **Review pure-site in target environments with [Pure served locally](https://github.com/pure-css/pure-site/blob/master/README.md#running-with-pure-served-locally)**
 
-    - [ ] IE 11
-    - [ ] Edge
-    - [ ] Chrome
-    - [ ] Firefox
-    - [ ] Safari
-    - [ ] iOS 10.x
-    - [ ] Android 4.x
-    - [ ] Android 5.x
+  - [ ] IE 11
+  - [ ] Edge
+  - [ ] Chrome
+  - [ ] Firefox
+  - [ ] Safari
+  - [ ] iOS 10.x
+  - [ ] Android 4.x
+  - [ ] Android 5.x
 
 - [ ] **Review HISTORY.md**
 
-    https://github.com/pure-css/pure/blob/master/HISTORY.md
+  https://github.com/pure-css/pure/blob/master/HISTORY.md
 
-    Make sure all the major changes since the last release of Pure are reflected in HISTORY.md entries.
+  Make sure all the major changes since the last release of Pure are reflected in HISTORY.md entries.
 
 ## Prepare repos for release
 
@@ -59,39 +59,36 @@ This assumes the following repo's are cloned and `npm` installed:
 
 - [ ] **Bump versions**
 
-    It should have already been determined whether this is a minor or patch version release. Update Pure's version number to the new version in the following places. You'll likely be dropping a "-pre" suffix which was in place during the last development cycle. Do not use a "v" in the version (e.g., 1.0.0):
+  It should have already been determined whether this is a minor or patch version release. Update Pure's version number to the new version in the following places. You'll likely be dropping a "-pre" suffix which was in place during the last development cycle. Do not use a "v" in the version (e.g., 1.0.0):
 
-    - [ ] package.json
-    - [ ] HISTORY.md (Update "NEXT")
-    - [ ] README.md (x2 CDN URLs)
+  - [ ] package.json
+  - [ ] HISTORY.md (Update "NEXT")
 
 - [ ] **Build Pure release files via `grunt release`**
 
-    Using Grunt, create the release/[version]/pure-[version].tar.gz file:
+  Using Grunt, create the release/[version]/pure-[version].tar.gz file:
 
-    ```
-    $ grunt release
-    ```
-
-    **Note:** If the build fails it's for a good reason, most likely because there's code which is not passing CSSLint. We should always fix these issues and never force a release.
+  ```bash
+  $ grunt release
+  ```
 
+  **Note:** If the build fails it's for a good reason, most likely because there's code which is not passing CSSLint. We should always fix these issues and never force a release.
 
 ## Publish pure to NPM
 
 From the `pure` repo run the following command to publish Pure to NPM. This will ensure `unpkg.com` CDN gets the new files.
 
-```
+```bash
 npm publish .
 ```
 
 Verify via https://unpkg.com/purecss@VERSION
 
-
 ## Draft releases on Github
 
 - [ ] **Draft a new release on [GitHub](https://github.com/pure-css/pure/releases) for all three repos,** using "v" in the version number (e.g., v1.0.0). Drafts are invisible to the public. Once these are published, the repos will be visible, and they will be tagged. **Don't publish them just yet.**
 
-    - [ ] **pure**
+  - [ ] **pure**
 
 ## Formally publish Pure
 
@@ -99,7 +96,7 @@ Now all our files are out there and everything is looking good.
 
 - [ ] **Publish pure**
 
-    From the [pure repo](https://github.com/pure-css/pure/releases), publish the release. This will tag the repo and signal to the public that the new Pure release is complete.
+  From the [pure repo](https://github.com/pure-css/pure/releases), publish the release. This will tag the repo and signal to the public that the new Pure release is complete.
 
 ## Spread the word
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "purecss",
-  "version": "2.0.5",
+  "version": "2.0.6",
   "repository": {
     "type": "git",
     "url": "git://github.com/pure-css/pure.git"
@@ -13,7 +13,9 @@
     "site:start": "cd site && npm run start",
     "test": "grunt test && tap test/*.js"
   },
-  "files": ["build/"],
+  "files": [
+    "build/"
+  ],
   "devDependencies": {
     "autoprefixer": "^9.8.6",
     "eslint": "^7.18.0",