Implement the new changelog tool in ckeditor5-angular #493
Description
Task description
It's time to roll out the new changelog generator in this repository, as the new solution is ready to use (ckeditor/ckeditor5#18051).
Definition of Done
- Upgrade all of the
ckeditor5-dev-*packages to their latest version.- When writing this, it's
v50.1.0. It's enough to match the major version (^50.0.0).
- When writing this, it's
- Add a script to create a new changelog entry (
nice, New Individual Changelog Entry)."nice": "ckeditor5-dev-changelog-create-entry"
- Redesign (and rename:
release:prepare-changelog) the changelog generator to use theckeditor5-dev-changelogpackage. It should accept two flags:--date- an optional modifier that defines a release day.--dry-run- an optional modifier that displays the changelog instead of saving it into theCHANGELOG.mdfile.
- Rewrite a pull request template to avoid mentioning the old convention.
- If the repository contains commits since the latest release, they must be converted into the new structure.
- Write a comment including the current status to give the reviewer a clear vision of what to expect.
- Create the changelog directory and a file that allows tracking it by git, even if it's empty.
.changelog/.gitkeep- Ensure git tracks changes in this directory.
- Review and update README.
- Rename
Devops=>Platform - Rewrite the section regarding the changelog preparation.
- Rename
Technical details
No response
Other details
- To determine if the repository contains commits since its latest release, use
npm run changelog -- --branch master. It prints the log. If there is any non-internal change, we must convert it. - An example PR introducing the same change in
ckeditor5-dev: Integrate the new changelog tool in the repository ckeditor5-dev#1149