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
Copy file name to clipboardExpand all lines: README.md
+9-25
Original file line number
Diff line number
Diff line change
@@ -71,31 +71,15 @@ Before releasing a new version, run a demo project to confirm that the integrati
71
71
3. Run `npm run test` to see if the project passes all automated tests.
72
72
4. Run `npm run build` to see if the project with the integration builds without errors.
73
73
74
-
### Changelog
75
-
76
-
Before starting the release process, you need to generate the changelog:
77
-
78
-
```bash
79
-
npm run changelog
80
-
```
81
-
82
-
### Publishing
83
-
84
-
After generating the changelog, you are able to release the package.
85
-
86
-
First, you need to bump the version:
87
-
88
-
```bash
89
-
npm run release:prepare-packages
90
-
```
91
-
92
-
After bumping the version, you can publish the changes:
93
-
94
-
```bash
95
-
npm run release:publish-packages
96
-
```
97
-
98
-
Note: The `release/` directory will be published.
74
+
This package's release process is automated via CircleCI. Before you start a new release, you'll need to prepare the changelog entries.
75
+
76
+
1. Make sure the `#master` branch is up-to-date: `git fetch && git checkout master && git pull`.
77
+
1. Prepare a release branch: `git checkout -b release-[YYYY-MM-DD]` where `YYYY-MM-DD` is the current day.
78
+
1. Generate the changelog entries: `yarn run changelog --branch release-[YYYY-MM-DD]`.
79
+
* This task checks what changed in each package and bumps the version accordingly. If nothing changes at all, it won't create a new changelog entry. If changes were irrelevant (e.g., only dependencies), it would make an "internal changes" entry.
80
+
* Scan the logs printed by the tool to search for errors (incorrect changelog entries). Incorrect entries (e.g., ones without the type) should be addressed. You may need to create entries for them manually. This is done directly in CHANGELOG.md (in the root directory). Make sure to verify the proposed version after you modify the changelog.
81
+
1. Commit all changes and prepare a new pull request targeting the `#master` branch.
82
+
1. Ping the @ckeditor/ckeditor-5-devops team to review the pull request and trigger the release process.
0 commit comments