Skip to content

Bump the ckeditor group with 2 updates - #173

Open
dependabot[bot] wants to merge 1 commit into
6.2from
dependabot/npm_and_yarn/ckeditor-01db756f03
Open

Bump the ckeditor group with 2 updates#173
dependabot[bot] wants to merge 1 commit into
6.2from
dependabot/npm_and_yarn/ckeditor-01db756f03

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 1, 2026

Copy link
Copy Markdown
Contributor

Bumps the ckeditor group with 2 updates: @ckeditor/ckeditor5-dev-build-tools and @ckeditor/ckeditor5-dev-utils.

Updates @ckeditor/ckeditor5-dev-build-tools from 63.0.0 to 63.1.0

Release notes

Sourced from @​ckeditor/ckeditor5-dev-build-tools's releases.

v63.1.0

Features

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

Bug fixes

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

Released packages

Check out the Versioning policy guide for more information.

Releases containing new features:

Other releases:

Changelog

Sourced from @​ckeditor/ckeditor5-dev-build-tools's changelog.

63.1.0 (October 28, 2026)

Features

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

Bug fixes

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

Released packages

Check out the Versioning policy guide for more information.

Releases containing new features:

Other releases:

Commits

Updates @ckeditor/ckeditor5-dev-utils from 63.0.0 to 63.1.0

Release notes

Sourced from @​ckeditor/ckeditor5-dev-utils's releases.

v63.1.0

Features

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

Bug fixes

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

Released packages

Check out the Versioning policy guide for more information.

Releases containing new features:

Other releases:

Changelog

Sourced from @​ckeditor/ckeditor5-dev-utils's changelog.

63.1.0 (October 28, 2026)

Features

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

Bug fixes

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

Released packages

Check out the Versioning policy guide for more information.

Releases containing new features:

Other releases:

Commits
  • 700d3bd Release: v63.1.0. [skip ci]
  • 959443f npm.checkVersionAvailability() rethrows errors that do not tell whether the...
  • b8efa5a Update dependencies.
  • See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
Bump the ckeditor group with 2 updates
1d4c822 
Bumps the ckeditor group with 2 updates: [@ckeditor/ckeditor5-dev-build-tools](https://github.com/ckeditor/ckeditor5-dev/tree/HEAD/packages/ckeditor5-dev-build-tools) and [@ckeditor/ckeditor5-dev-utils](https://github.com/ckeditor/ckeditor5-dev/tree/HEAD/packages/ckeditor5-dev-utils).


Updates `@ckeditor/ckeditor5-dev-build-tools` from 63.0.0 to 63.1.0
- [Release notes](https://github.com/ckeditor/ckeditor5-dev/releases)
- [Changelog](https://github.com/ckeditor/ckeditor5-dev/blob/master/CHANGELOG.md)
- [Commits](https://github.com/ckeditor/ckeditor5-dev/commits/v63.1.0/packages/ckeditor5-dev-build-tools)

Updates `@ckeditor/ckeditor5-dev-utils` from 63.0.0 to 63.1.0
- [Release notes](https://github.com/ckeditor/ckeditor5-dev/releases)
- [Changelog](https://github.com/ckeditor/ckeditor5-dev/blob/master/CHANGELOG.md)
- [Commits](https://github.com/ckeditor/ckeditor5-dev/commits/v63.1.0/packages/ckeditor5-dev-utils)

---
updated-dependencies:
- dependency-name: "@ckeditor/ckeditor5-dev-build-tools"
  dependency-version: 63.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: ckeditor
- dependency-name: "@ckeditor/ckeditor5-dev-utils"
  dependency-version: 63.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: ckeditor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Nov 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants