markdownlint 0.32.1 → 0.34.0

package/CHANGELOG.md

@@ -1,5 +1,22 @@
 # Changelog
 
+## 0.34.0
+
+- Use `micromark` in MD027/MD028/MD036/MD040/MD041/MD046/MD048
+- Improve MD013/MD034/MD049/MD050/MD051
+- Update custom rule requirements and documentation
+- Improve various TypeScript declarations
+- Update dependencies
+
+## 0.33.0
+
+- Add MD055/table-pipe-style, MD056/table-column-count
+- Improve MD005/MD007/MD024/MD026/MD038
+- Incorporate `micromark-extension-directive`
+- Improve JSON schema, document validation
+- Reduce size of browser script
+- Update dependencies
+
 ## 0.32.1
 
 - Fix behavior of MD054
@@ -13,6 +30,7 @@
 - Improve MD022/MD026/MD034/MD037/MD038/MD045/MD051
 - Improve JSON schema and related examples
 - Provide type declaration for Configuration object
+- Remove support for end-of-life Node version 16
 - Update dependencies
 
 ## 0.31.1

package/CONTRIBUTING.md

@@ -19,8 +19,9 @@ project's only dependencies.
 
 Package versions for `dependencies` and `devDependencies` should be specified
 exactly (also known as "pinning"). The short explanation is that doing otherwise
-eventually leads to inconsistent behavior and broken functionality. (See [Pin
-your npm/yarn dependencies][pin-dependencies] for a longer explanation.)
+eventually leads to inconsistent behavior and broken functionality. (See [Why I
+pin dependency versions in Node.js packages][version-pinning] for a longer
+explanation.)
 
 If developing a new rule, start by creating a [custom rule][custom-rules] in its
 own project. Once written, published, and tested in real world scenarios, open
@@ -88,5 +89,5 @@ Thank you!
 [micromark]: https://www.npmjs.com/package/micromark
 [new-rule]: https://github.com/DavidAnson/markdownlint/labels/new%20rule
 [npm-scripts]: https://docs.npmjs.com/misc/scripts
-[pin-dependencies]: https://maxleiter.com/blog/pin-dependencies
 [rewriting-history]: https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History
+[version-pinning]: https://dlaa.me/blog/post/versionpinning

package/README.md

@@ -134,6 +134,8 @@ playground for learning and exploring.
 - **[MD052](doc/md052.md)** *reference-links-images* - Reference links and images should use a label that is defined
 - **[MD053](doc/md053.md)** *link-image-reference-definitions* - Link and image reference definitions should be needed
 - **[MD054](doc/md054.md)** *link-image-style* - Link and image style
+- **[MD055](doc/md055.md)** *table-pipe-style* - Table pipe style
+- **[MD056](doc/md056.md)** *table-column-count* - Table column count
 
 <!-- markdownlint-restore -->
 
@@ -175,6 +177,7 @@ rules at once.
 - **`ol`** - `MD029`, `MD030`, `MD032`
 - **`spaces`** - `MD018`, `MD019`, `MD020`, `MD021`, `MD023`
 - **`spelling`** - `MD044`
+- **`table`** - `MD055`, `MD056`
 - **`ul`** - `MD004`, `MD005`, `MD007`, `MD030`, `MD032`
 - **`url`** - `MD034`
 - **`whitespace`** - `MD009`, `MD010`, `MD012`, `MD027`, `MD028`, `MD030`,
@@ -403,6 +406,9 @@ See [markdownlint-config-schema.json](schema/markdownlint-config-schema.json)
 for the [JSON Schema](https://json-schema.org/) of the `options.config`
 object.
 
+See [ValidatingConfiguration.md](schema/ValidatingConfiguration.md) for ways to
+use the JSON Schema to validate configuration.
+
 For more advanced scenarios, styles can reference and extend other styles.
 The `readConfig` and `readConfigSync` functions can be used to read such
 styles.