chore: release main (#35)

🤖 I have created a release *beep* *boop*
---


<details><summary>markdown: 1.3.0</summary>

##
[1.3.0](markdown-v1.2.0...markdown-v1.3.0)
(2024-05-06)


### Features

* Update packages
([744d6a7](744d6a7))
</details>

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

.release-please-manifest.json

@@ -2,5 +2,5 @@
   "packages/base": "1.3.0",
   "packages/react": "1.6.0",
   "packages/next": "1.4.0",
-  "packages/markdown": "1.2.0"
+  "packages/markdown": "1.3.0"
 }

packages/markdown/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## [1.3.0](https://github.com/Pilaton/eslint-eco/compare/markdown-v1.2.0...markdown-v1.3.0) (2024-05-06)
+
+
+### Features
+
+* Update packages ([744d6a7](https://github.com/Pilaton/eslint-eco/commit/744d6a7820c0311c18a7f635f1041300a0f24fb9))
+
 ## [1.2.0](https://github.com/Pilaton/eslint-eco/compare/markdown-v1.1.0...markdown-v1.2.0) (2024-03-04)
 
 

packages/markdown/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pilaton/eslint-config-markdown",
-  "version": "1.2.0",
+  "version": "1.3.0",
   "description": "ESLint configuration for checking markdown files",
   "keywords": [
     "eslint",