You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Replace all @ts-ignore comments with @ts-expect-error for stricter
type suppression across 6 files. Run Prettier to fix formatting drift.
Nightshift-Task: lint-fix
Nightshift-Ref: https://github.com/marcus/nightshift
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,10 +55,10 @@ This diagram illustrates the release workflow for the BlockNote monorepo.
55
55
56
56
Essentially, when the maintainers have decided to release a new version of BlockNote, they will:
57
57
58
-
1. Check that the `main` branch is in a releasable state:
58
+
1. Check that the `main` branch is in a releasable state:
59
59
- CI status of main branch is green
60
60
- Builds are passing
61
-
2. Bump the package versions using the `pnpm run deploy` command. This command will:
61
+
2. Bump the package versions using the `pnpm run deploy` command. This command will:
62
62
1. Based on semantic versioning, determine the next version number.
63
63
2. Apply the new version number to all publishable packages within the monorepo.
64
64
3. Generate a changelog for the new version.
@@ -80,8 +80,8 @@ The release workflow will:
80
80
81
81
From time to time, you may need to publish a new package to npm. To do this, you cannot just deploy the package to npm, you need to:
82
82
83
-
1. Run `nx release version --dry-run` and check that the version number is correct for the package.
83
+
1. Run `nx release version --dry-run` and check that the version number is correct for the package.
84
84
- Once this is done, you can run `nx release version` to actually apply the version bump locally (staged to your local git repo).
85
-
2. Run `nx release changelog --from <prev-version> <new-version> --dry-run` and check that the changelog is correct for the package.
85
+
2. Run `nx release changelog --from <prev-version> <new-version> --dry-run` and check that the changelog is correct for the package.
86
86
- Once this is done, you can run the same command without the `--dry-run` flag to actually apply the changelog, commit & push the changes to the `main` branch.
87
-
3. The release workflow will automatically publish the package to npm.
87
+
3. The release workflow will automatically publish the package to npm.
0 commit comments