CKEditor 5 linters configuration

Issue tracker

The issue tracker is located in the ckeditor/ckeditor5 repository.

Packages

This repository is a monorepo. It contains multiple npm packages.

Package	Version	Dependencies
eslint-config-ckeditor5
eslint-plugin-ckeditor5-rules
stylelint-config-ckeditor5
stylelint-plugin-ckeditor5-rules

Archived repositories

Some of the packages in this repository were previously separate repositories, and are now archived:

• eslint-config-ckeditor5
• eslint-plugin-ckeditor5-rules
• stylelint-config-ckeditor5

Cloning

1. Clone this repository.
2. Do yarn install inside (this package uses yarn workspaces).
3. You're ready to go!

Testing

Tests:

yarn run test

Releasing packages

CircleCI automates the release process and can release both channels: stable (X.Y.Z) and pre-releases (X.Y.Z-alpha.X, etc.).

Before you start, you need to prepare the changelog entries.

1. Make sure the #master branch is up-to-date: git fetch && git checkout master && git pull.
2. Prepare a release branch: git checkout -b release-[YYYYMMDD] where YYYYMMDD is the current day.
3. Generate the changelog entries: yarn run changelog --branch release-[YYYYMMDD] [--from [GIT_TAG]].

   • By default, the changelog generator uses the latest published tag as a starting point for collecting commits to process.

     The --from modifier option allows overriding the default behavior. It is required when preparing the changelog entries for the next stable release while the previous one was marked as a prerelease, e.g., @alpha.

     Example: Let's assume that the v40.5.0-alpha.0 tag is our latest and that we want to release it on a stable channel. The --from modifier should be equal to --from v40.4.0.

   • This task checks what changed in each package and bumps the version accordingly. It won't create a new changelog entry if nothing changes at all. If changes were irrelevant (e.g., only dependencies), it would make an "internal changes" entry.

   • 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.

4. Commit all changes and prepare a new pull request targeting the #master branch.
5. Ping the @ckeditor/ckeditor-5-devops team to review the pull request and trigger the release process.

License

Licensed under the terms of MIT license. For full details about the license, please check the LICENSE.md file.