@doist/typist 10.0.0 → 10.0.1

package/CHANGELOG.md

@@ -1,3 +1,9 @@
+## [10.0.1](https://github.com/Doist/typist/compare/v10.0.0...v10.0.1) (2026-04-08)
+
+### Bug Fixes
+
+- add contents read permission for CI validation workflow ([#1292](https://github.com/Doist/typist/issues/1292)) ([d3cb224](https://github.com/Doist/typist/commit/d3cb2243e7f6fc732b6a2c76b8f854ae4eda09dc))
+
 ## [10.0.0](https://github.com/Doist/typist/compare/v9.0.3...v10.0.0) (2026-03-12)
 
 ### ⚠ BREAKING CHANGES

package/CONTRIBUTING.md

@@ -72,7 +72,7 @@ The release process for Typist is fully automated with [`semantic-release`](http
 
 To test features before publishing a stable release:
 
-1. **Sync `next` with `main`** if they are out of sync, before starting new work:
+1. **Sync `next` with `main`** before starting new work, and after each stable release (required for `semantic-release` to correctly initiate the next pre-release versioning cycle):
 
     ```sh
     git checkout next
@@ -86,14 +86,6 @@ To test features before publishing a stable release:
 
 4. **Promote to stable:** When ready, open a PR to merge `next` into `main`. The PR title must follow [Conventional Commits](https://www.conventionalcommits.org/) (e.g., `feat: ...`, `fix: ...`) as it determines the version bump for the stable release.
 
-5. **Sync `next` with `main`** after the stable release, to pull back the release commit:
-
-    ```sh
-    git checkout next
-    git merge main -m "chore: sync next with main [skip ci]"
-    git push origin next
-    ```
-
 > **Note:** The `CHANGELOG.md` is only updated for stable releases on `main`. Pre-releases still get GitHub release notes and npm publication.
 
 ### Visual Studio Code
@@ -144,6 +136,16 @@ Commit types, such as `feat:` or `fix:`, are the only ones that will affect vers
 
 A commit that has the text `BREAKING CHANGE:` at the beginning of its optional body or footer section, or appends a `!` after the type/scope, introduces a breaking API change (correlating with `MAJOR` in Semantic Versioning). A breaking change can be part of commits of any _type_.
 
+#### How Commits Map to the CHANGELOG
+
+The commit **header** (subject line) and footer metadata — including `BREAKING CHANGE:` notes and issue references (e.g., `Closes #123`) — are used to generate the `CHANGELOG.md`. The commit body is ignored by the changelog generator.
+
+When squash-merging a PR, GitHub lets you edit the commit message and extended description. Keep the following in mind:
+
+- The **commit message** (header) becomes the entry under its type section (e.g., Features, Bug Fixes).
+- A `BREAKING CHANGE:` **footer** in the extended description becomes a separate entry in the Breaking Changes section. Use it to describe the impact for consumers.
+- Using `!` in the header without a `BREAKING CHANGE:` footer will duplicate the subject line in both the type section and the Breaking Changes section. To avoid this, always include a `BREAKING CHANGE:` footer with a distinct description when introducing breaking changes.
+
 ## License
 
 By contributing to Typist, you agree that your contributions will be licensed under its [MIT license](LICENSE).

package/package.json

@@ -1,7 +1,7 @@
 {
     "name": "@doist/typist",
     "description": "The mighty Tiptap-based rich-text editor React component that powers Doist products.",
-    "version": "10.0.0",
+    "version": "10.0.1",
     "license": "MIT",
     "homepage": "https://typist.doist.dev/",
     "repository": {
@@ -93,14 +93,14 @@
     "devDependencies": {
         "@doist/eslint-config": "12.0.0",
         "@doist/prettier-config": "4.0.1",
-        "@doist/reactist": "30.0.1",
+        "@doist/reactist": "30.1.0",
         "@mdx-js/react": "3.1.1",
         "@semantic-release/changelog": "6.0.3",
         "@semantic-release/exec": "7.1.0",
         "@semantic-release/git": "10.0.1",
-        "@storybook/addon-a11y": "10.2.16",
-        "@storybook/addon-docs": "10.2.16",
-        "@storybook/react-vite": "10.2.16",
+        "@storybook/addon-a11y": "10.3.3",
+        "@storybook/addon-docs": "10.3.3",
+        "@storybook/react-vite": "10.3.3",
         "@testing-library/dom": "10.4.1",
         "@testing-library/jest-dom": "6.9.1",
         "@testing-library/react": "16.3.2",
@@ -111,7 +111,7 @@
         "@types/react-syntax-highlighter": "15.5.13",
         "@types/turndown": "5.0.6",
         "@types/unist": "3.0.3",
-        "@vitejs/plugin-react": "5.1.4",
+        "@vitejs/plugin-react": "5.2.0",
         "boring-avatars": "2.0.4",
         "classnames": "2.5.1",
         "conventional-changelog-conventionalcommits": "9.3.0",
@@ -128,9 +128,9 @@
         "husky": "9.1.7",
         "ignore-sync": "8.0.0",
         "is-ci": "4.1.0",
-        "jsdom": "28.1.0",
-        "lint-staged": "16.3.2",
-        "npm-run-all-next": "1.2.3",
+        "jsdom": "29.0.1",
+        "lint-staged": "16.4.0",
+        "npm-run-all-next": "1.2.5",
         "prettier": "3.8.1",
         "publint": "0.3.18",
         "react": "18.3.1",
@@ -143,14 +143,14 @@
         "remark-gfm": "4.0.1",
         "rimraf": "6.1.3",
         "semantic-release": "25.0.3",
-        "storybook": "10.2.16",
+        "storybook": "10.3.3",
         "storybook-css-modules": "1.0.8",
         "tippy.js": "6.3.7",
-        "tsdown": "0.21.2",
-        "type-fest": "5.4.4",
+        "tsdown": "0.21.4",
+        "type-fest": "5.5.0",
         "typescript": "5.9.3",
         "typescript-plugin-css-modules": "5.2.0",
-        "vitest": "4.0.18"
+        "vitest": "4.1.1"
     },
     "peerDependencies": {
         "emoji-regex": "^10.2.1",