Bump version to 1.0.0

Co-Authored-By: Romaric <romaric.pascal@digital.cabinet-office.gov.uk>

CHANGELOG.md

@@ -6,6 +6,42 @@
   useful summary for people upgrading their application, not a replication
   of the commit log.
 
+## 1.0.0
+
+This release upgrades to Stylelint 15 and now includes:
+
+* Checks for media query syntax, rules and values
+* Checks for number precision inside CSS functions
+* Fixes for duplicate rules with intentionally different units
+
+Read about breaking changes in the Stylelint [**Migrating to v15.0.0**](https://github.com/stylelint/stylelint/blob/main/docs/migration-guide/to-15.md#breaking-changes) guide.
+
+### Support for Internet Explorer 8, 9 and 10
+
+Support for IE8–10 has not been a requirement for services since June 2018, so we removed the rule [`selector-pseudo-element-colon-notation`](https://stylelint.io/user-guide/rules/selector-pseudo-element-colon-notation/) preventing double-colon `::before` and `::after` pseudo element notation.
+
+This change was made in [pull request #36: Remove `selector-pseudo-element-colon-notation`](https://github.com/alphagov/stylelint-config-gds/pull/36).
+
+### Checking for invalid property/value pairs
+
+Stylelint 15 adds an optional new rule [`declaration-property-value-no-unknown`](https://stylelint.io/user-guide/rules/declaration-property-value-no-unknown) to check for invalid property/value combinations such as:
+
+```css
+.govuk-link--example {
+  top: red;
+}
+```
+
+Do try it on your projects before we enable it in future, but [report any problems on this issue](https://github.com/alphagov/stylelint-config-gds/issues/42) to help us assess its impact.
+
+### Deprecated stylistic rules
+
+As mentioned in the [`stylelint-config-gds@0.3.0` release notes](#030) below, this release [deprecates all stylistic rules](https://stylelint.io/migration-guide/to-15/#deprecated-stylistic-rules). We no longer include rules that would format your styles and recommend you use [Prettier](https://prettier.io/) for formatting instead.
+
+>When we created these rules, pretty printers (like Prettier) didn't exist. They now offer a better way to consistently format code, especially whitespace. Linters and pretty printers are complementary tools that work together to help you write consistent and error-free code.
+
+If this is not possible, you can configure the [`stylelint-stylistic`](https://github.com/elirasza/stylelint-stylistic) or [`stylelint-codeguide`](https://github.com/firefoxic/stylelint-codeguide) plugins to restore the [deprecated rules](https://github.com/alphagov/stylelint-config-gds/pull/32/commits/0bab4e7596d642c6fa65bc133e24968a4ff74671) instead.
+
 ## 0.3.0
 
 This release updates all bundled configs to the maximum version supported by Stylelint 14. This work is in preparation for [Stylelint 15 deprecating all stylistic rules](https://stylelint.io/migration-guide/to-15/#deprecated-stylistic-rules) with a recommendation to use Prettier for formatting.

package.json

@@ -1,6 +1,6 @@
 {
   "name": "stylelint-config-gds",
-  "version": "0.3.0",
+  "version": "1.0.0",
   "description": "A Stylelint configuration for the UK Government Digital Service.",
   "main": "scss.js",
   "scripts": {