@doist/typist 10.0.0-next.2 → 10.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +18 -0
- package/CONTRIBUTING.md +11 -9
- package/package.json +13 -13
package/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,21 @@
|
|
|
1
|
+
## [10.0.1](https://github.com/Doist/typist/compare/v10.0.0...v10.0.1) (2026-04-08)
|
|
2
|
+
|
|
3
|
+
### Bug Fixes
|
|
4
|
+
|
|
5
|
+
- add contents read permission for CI validation workflow ([#1292](https://github.com/Doist/typist/issues/1292)) ([d3cb224](https://github.com/Doist/typist/commit/d3cb2243e7f6fc732b6a2c76b8f854ae4eda09dc))
|
|
6
|
+
|
|
7
|
+
## [10.0.0](https://github.com/Doist/typist/compare/v9.0.3...v10.0.0) (2026-03-12)
|
|
8
|
+
|
|
9
|
+
### ⚠ BREAKING CHANGES
|
|
10
|
+
|
|
11
|
+
- The package is now declared as ESM ("type": "module")
|
|
12
|
+
and uses an exports map. Deep imports (e.g. @doist/typist/dist/...) are
|
|
13
|
+
no longer supported. Minimum Node.js version is now 22.18.0.
|
|
14
|
+
|
|
15
|
+
### Features
|
|
16
|
+
|
|
17
|
+
- modernize package publishing and build tooling ([#1255](https://github.com/Doist/typist/issues/1255)) ([1c8a194](https://github.com/Doist/typist/commit/1c8a194cbbdac1548281717133f36d730c97ea29))
|
|
18
|
+
|
|
1
19
|
## [9.0.3](https://github.com/Doist/typist/compare/v9.0.2...v9.0.3) (2026-02-25)
|
|
2
20
|
|
|
3
21
|
### Bug Fixes
|
package/CONTRIBUTING.md
CHANGED
|
@@ -72,7 +72,7 @@ The release process for Typist is fully automated with [`semantic-release`](http
|
|
|
72
72
|
|
|
73
73
|
To test features before publishing a stable release:
|
|
74
74
|
|
|
75
|
-
1. **Sync `next` with `main`**
|
|
75
|
+
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):
|
|
76
76
|
|
|
77
77
|
```sh
|
|
78
78
|
git checkout next
|
|
@@ -86,14 +86,6 @@ To test features before publishing a stable release:
|
|
|
86
86
|
|
|
87
87
|
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.
|
|
88
88
|
|
|
89
|
-
5. **Sync `next` with `main`** after the stable release, to pull back the release commit:
|
|
90
|
-
|
|
91
|
-
```sh
|
|
92
|
-
git checkout next
|
|
93
|
-
git merge main -m "chore: sync next with main [skip ci]"
|
|
94
|
-
git push origin next
|
|
95
|
-
```
|
|
96
|
-
|
|
97
89
|
> **Note:** The `CHANGELOG.md` is only updated for stable releases on `main`. Pre-releases still get GitHub release notes and npm publication.
|
|
98
90
|
|
|
99
91
|
### Visual Studio Code
|
|
@@ -144,6 +136,16 @@ Commit types, such as `feat:` or `fix:`, are the only ones that will affect vers
|
|
|
144
136
|
|
|
145
137
|
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_.
|
|
146
138
|
|
|
139
|
+
#### How Commits Map to the CHANGELOG
|
|
140
|
+
|
|
141
|
+
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.
|
|
142
|
+
|
|
143
|
+
When squash-merging a PR, GitHub lets you edit the commit message and extended description. Keep the following in mind:
|
|
144
|
+
|
|
145
|
+
- The **commit message** (header) becomes the entry under its type section (e.g., Features, Bug Fixes).
|
|
146
|
+
- 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.
|
|
147
|
+
- 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.
|
|
148
|
+
|
|
147
149
|
## License
|
|
148
150
|
|
|
149
151
|
By contributing to Typist, you agree that your contributions will be licensed under its [MIT license](LICENSE).
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@doist/typist",
|
|
3
3
|
"description": "The mighty Tiptap-based rich-text editor React component that powers Doist products.",
|
|
4
|
-
"version": "10.0.
|
|
4
|
+
"version": "10.0.1",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"homepage": "https://typist.doist.dev/",
|
|
7
7
|
"repository": {
|
|
@@ -93,14 +93,14 @@
|
|
|
93
93
|
"devDependencies": {
|
|
94
94
|
"@doist/eslint-config": "12.0.0",
|
|
95
95
|
"@doist/prettier-config": "4.0.1",
|
|
96
|
-
"@doist/reactist": "30.0
|
|
96
|
+
"@doist/reactist": "30.1.0",
|
|
97
97
|
"@mdx-js/react": "3.1.1",
|
|
98
98
|
"@semantic-release/changelog": "6.0.3",
|
|
99
99
|
"@semantic-release/exec": "7.1.0",
|
|
100
100
|
"@semantic-release/git": "10.0.1",
|
|
101
|
-
"@storybook/addon-a11y": "10.
|
|
102
|
-
"@storybook/addon-docs": "10.
|
|
103
|
-
"@storybook/react-vite": "10.
|
|
101
|
+
"@storybook/addon-a11y": "10.3.3",
|
|
102
|
+
"@storybook/addon-docs": "10.3.3",
|
|
103
|
+
"@storybook/react-vite": "10.3.3",
|
|
104
104
|
"@testing-library/dom": "10.4.1",
|
|
105
105
|
"@testing-library/jest-dom": "6.9.1",
|
|
106
106
|
"@testing-library/react": "16.3.2",
|
|
@@ -111,7 +111,7 @@
|
|
|
111
111
|
"@types/react-syntax-highlighter": "15.5.13",
|
|
112
112
|
"@types/turndown": "5.0.6",
|
|
113
113
|
"@types/unist": "3.0.3",
|
|
114
|
-
"@vitejs/plugin-react": "5.
|
|
114
|
+
"@vitejs/plugin-react": "5.2.0",
|
|
115
115
|
"boring-avatars": "2.0.4",
|
|
116
116
|
"classnames": "2.5.1",
|
|
117
117
|
"conventional-changelog-conventionalcommits": "9.3.0",
|
|
@@ -128,9 +128,9 @@
|
|
|
128
128
|
"husky": "9.1.7",
|
|
129
129
|
"ignore-sync": "8.0.0",
|
|
130
130
|
"is-ci": "4.1.0",
|
|
131
|
-
"jsdom": "
|
|
132
|
-
"lint-staged": "16.
|
|
133
|
-
"npm-run-all-next": "1.2.
|
|
131
|
+
"jsdom": "29.0.1",
|
|
132
|
+
"lint-staged": "16.4.0",
|
|
133
|
+
"npm-run-all-next": "1.2.5",
|
|
134
134
|
"prettier": "3.8.1",
|
|
135
135
|
"publint": "0.3.18",
|
|
136
136
|
"react": "18.3.1",
|
|
@@ -143,14 +143,14 @@
|
|
|
143
143
|
"remark-gfm": "4.0.1",
|
|
144
144
|
"rimraf": "6.1.3",
|
|
145
145
|
"semantic-release": "25.0.3",
|
|
146
|
-
"storybook": "10.
|
|
146
|
+
"storybook": "10.3.3",
|
|
147
147
|
"storybook-css-modules": "1.0.8",
|
|
148
148
|
"tippy.js": "6.3.7",
|
|
149
|
-
"tsdown": "0.21.
|
|
150
|
-
"type-fest": "5.
|
|
149
|
+
"tsdown": "0.21.4",
|
|
150
|
+
"type-fest": "5.5.0",
|
|
151
151
|
"typescript": "5.9.3",
|
|
152
152
|
"typescript-plugin-css-modules": "5.2.0",
|
|
153
|
-
"vitest": "4.
|
|
153
|
+
"vitest": "4.1.1"
|
|
154
154
|
},
|
|
155
155
|
"peerDependencies": {
|
|
156
156
|
"emoji-regex": "^10.2.1",
|