Release v63.1.0 · ckeditor/ckeditor5-dev

release-tools: publishPackages() accepts the staging-v{version} npm tag for a stable release when {version} is the exact package version, for example staging-v1.2.3 for v1.2.3. It lets several release lines stage their packages at the same time without moving one shared staging tag.
release-tools: Added the removeNpmTags() function. It removes an npm dist-tag from all given packages, for example, a temporary tag used to stage a release. It works like reassignNpmTags(): it supports npm Trusted Publishing (OIDC), retries failed packages, and rejects after all packages have been processed when any of them failed. Packages that do not have the tag are reported as skipped, so it can be run again after a partial failure.

release-tools: getVersionForTag() no longer returns null when the npm registry cannot answer, for example, when it cannot be reached. It returns null only when the registry says that the tag or the package does not exist, and it rethrows any other error. Before, a network error looked like a missing tag. Then isLatestOrNextStableVersion() treated any version as the newest one, so a script could move the latest tag to an older release line.
utils: npm.checkVersionAvailability() no longer reports a version as available when the npm registry cannot answer, for example, when it cannot be reached. It resolves to true only when the registry says that the version or the package does not exist, and it rethrows any other error. Before, a network error made an already published version look available. publishPackages() and the changelog version prompt use this check, so they now fail with the network error instead of continuing.

Check out the Versioning policy guide for more information.

Released packages (summary)

Releases containing new features:

Other releases:

Navigation Menu