Skip to content

v63.0.0

Choose a tag to compare

@CKEditorBot CKEditorBot released this 23 Oct 09:43
· 16 commits to master since this release
v63.0.0
9e35099

MAJOR BREAKING CHANGES ℹ️

MINOR BREAKING CHANGES ℹ️

  • agents: Published runs now commit with the git configuration of the checkout: its author and its signing setup, for example the bot configured in CI. AI_TASKS_GIT_NAME and AI_TASKS_GIT_EMAIL still override the author. Publishing fails with a clear message when no author is configured. See ckeditor/ckeditor5-internal#4687.
  • agents: Published runs now stack their report pull requests. While report pull requests of a task are open, every run that finds something new opens one more, based on the one below it, so each pull request shows only the changes of its run. Previously, every run added its commits to the one open pull request. Before a run, the base branch is merged into the bottom branch and every branch into the next one, and a pull request whose base was merged is based on the right branch again. The next parts of a stack are named ai-tasks/<task>/<target>/<branch>--<part>. Merge the report pull requests from the bottom up, with a merge commit. Publishing from a base branch whose name ends with --<number> now fails, because its report branches would be mistaken for the parts of another stack. On a part of a stack, reject and dismiss fetch the parts below it from origin and revert a fix against the right one. See ckeditor/ckeditor5-internal#4687.

Features

  • agents: Published runs can tell Slack about every new report pull request. Set AI_TASKS_SLACK_WEBHOOK_URL to a Slack incoming webhook. A failed notification is reported as a problem of the run and does not fail it. See ckeditor/ckeditor5-internal#4687.

Bug fixes

  • ci: The ckeditor5-dev-ci-circle-disable-auto-cancel-builds and ckeditor5-dev-ci-circle-enable-auto-cancel-builds scripts now fail with a clear error message when CircleCI rejects the request with a non-2xx response. Previously, the scripts reported success even when the "Auto-cancel redundant workflows" option was not updated, which allowed a new push to cancel a running release workflow.

  • release-tools: The reassignNpmTags() task now rejects when the npm dist-tag could not be changed for at least one package. Before, the task only listed the errors in the output and resolved successfully, so release automation reported a success even though the tag was not moved.

    The task still processes all packages, retries each failed call, and prints the list of errors. Packages whose tag already points to the requested version are still reported as skipped and do not cause a rejection. The error message lists the packages that failed.

Other changes

Released packages

Check out the Versioning policy guide for more information.

Released packages (summary)

Major releases (contain major breaking changes):