Skip to content

Rephrase LTS-related communications#20106

Open
marburek wants to merge 3 commits intostable-v47from
fix-lts-communications
Open

Rephrase LTS-related communications#20106
marburek wants to merge 3 commits intostable-v47from
fix-lts-communications

Conversation

@marburek
Copy link
Copy Markdown
Contributor

🚀 Summary

Rephrase LTS-related communications.


📌 Related issues

  • Closes #000

💡 Additional information

Optional: Notes on decisions, edge cases, or anything helpful for reviewers.


🧾 Checklists

Use the following checklists to ensure important areas were not overlooked.
This does not apply to feature-branch merges.
If an item is not relevant to this type of change, simply leave it unchecked.

Author checklist

  • Is the changelog entry intentionally omitted?
  • Is the change backward-compatible?
  • Have you considered the impact on different editor setups and core interactions? (e.g., classic/inline/multi-root/many editors, typing, selection, paste, tables, lists, images, collaboration, pagination)
  • Has the change been manually verified in the relevant setups?
  • Does this change affect any of the above?
  • Is performance impacted?
  • Is accessibility affected?
  • Have tests been added that fail without this change (against regression)?
  • Have the API documentation, guides, feature digest, and related feature sections been updated where needed?
  • Have metadata files (ckeditor5-metadata.json) been updated if needed?
  • Are there any changes the team should be informed about (e.g. architectural, difficult to revert in future versions or having impact on other features)?
  • Were these changes documented (in Logbook)?

Reviewer checklist

  • PR description explains the changes and the chosen approach (especially when performance, API, or UX is affected).
  • The changelog entry is clear, user‑ or integrator-facing, and it describes any breaking changes.
  • All new external dependencies have been approved and mentioned in LICENSE.md (if any).
  • All human-readable, translateable strings in this PR been introduced using t() (if any).
  • I manually verified the change (e.g., in manual tests or documentation).
  • The target branch is correct.

@marburek marburek changed the title Added LTS release line mention to changelog. Rephrase LTS-related communications Apr 24, 2026
* If you did not intend to use LTS, please switch to non-LTS edition, for example,
* the [latest](https://ckeditor.com/docs/ckeditor5/latest/updating/guides/changelog.html) build.
* If you did not intend to use LTS, please note that all releases in the v47.7 line are
* for LTS subscribers only. To use a non-LTS edition, either upgrade to v48 or newer,
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* for LTS subscribers only. To use a non-LTS edition, either upgrade to v48 or newer,
* for LTS subscribers only. To use a non-LTS edition, either upgrade to v48 or later,

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure, just checking the vibe.

Comment thread packages/ckeditor5-core/src/editor/editor.ts Outdated
Co-authored-by: Witek Socha <w.socha@cksource.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants