Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency @ckeditor/ckeditor5-react to v9 #1532

Merged
merged 6 commits into from
Oct 17, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 7, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@ckeditor/ckeditor5-react ^7.0.0 -> ^9.0.0 age adoption passing confidence

Release Notes

ckeditor/ckeditor5-react (@​ckeditor/ckeditor5-react)

v9.2.0

Compare Source

Features
  • Experimental: Improve result type of useCKEditorCloud to make CKEditorPremiumFeatures and CKBox non-nullable when proper configuration is passed. (commit)
Other changes
  • Experimental: Rename the languages configuration property to translations in useCKEditorCloud. (commit)

v9.1.0

Compare Source

We added an onChangeInitializedEditors callback to CKEditorContext component to allow tracking newly initialized editors within the JSX React tree.

Example

<CKEditorContext
  context={ ClassicEditor.Context }
  contextWatchdog={ ClassicEditor.ContextWatchdog }
  onChangeInitializedEditors={ editors => {
    console.log( editors );
  }}
>
  <CKEditor
    editor={ ClassicEditor }
    data="<h2>Editor</h2>"
    contextItemMetadata={{
      name: 'editor1',
      user: { id: '2' }
    }}
  />

  <CKEditor
    editor={ ClassicEditor }
    data="<h2>Another Editor</h2><p>... in a common Context</p>"
    contextItemMetadata={{
      name: 'editor2'
    }}
  />
</CKEditorContext>

onChangeInitializedEditors will be called twice in the example above:

  1. First log: { editor1: ... }
  2. Second log: { editor1: ..., editor2: ... }

⚠️ Order of initialization is not guaranteed. editor2 might be initialized before editor1.

Features
  • Add an onChangeInitializedEditors callback to CKEditorContext to allow tracking of newly initialized editors within the JSX React tree. Closes #​513. (commit)
  • Experimental: Added useCKEditorCloud hook for managing asynchronous loading of CKEditor from a CDN. (commit)
  • Experimental: Added withCKEditorCloud HOC to simplify CKEditor integration with CDN in React components. (commit)
Bug fixes
  • Image upload should be now possible in demos. (commit)
  • Indent button is no longer disabled in manual demos. (commit)
  • Manual demos should point to existing documentation links. (commit)

v9.0.0

Compare Source

We are excited to announce a new major release of the React integration.

In this release, we have introduced the following breaking changes that should make using the integration more intuitive and easier.

  • ESM-first: Besides the UMD build, the integration is now available in ESM format. In most projects, the new ESM build should be automatically prioritized by bundlers and other tools.
  • Support for React 19: We improved support for using the integration in React 19. As a result, the <CKEditorContext> component and the useMultiRootEditor hook should no longer throw errors.
  • New name of the global variable: The name of the global variable used in the UMD build changed from CKEditor to CKEDITOR_REACT.
BREAKING CHANGES
  • Change the global name used in the UMD build from CKEditor to CKEDITOR_REACT.
Bug fixes
  • Adjusted CKEditorContext format to prevent race conditions in the CKEditor component. (commit)
  • Change JSX runtime to classic so that react-jsx-runtime is not bundled. (commit)
  • Change the global name used in the UMD build from CKEditor to CKEDITOR_REACT to match the new convention. See ckeditor/ckeditor5#16736. (commit)
Other changes
  • Added support for React 19. (commit)
  • Updated yarn.lock to fix dependabot alert. (commit)

v8.0.0

Compare Source

We are excited to announce the next major version of the React integration.

This release is intended to allow the integration to work with the latest version of new installation methods.


Configuration

📅 Schedule: Branch creation - "every weekend" in timezone US/Eastern, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/ckeditor-ckeditor5-react-9.x branch 17 times, most recently from 1f4d1eb to 2dfa474 Compare September 13, 2024 19:57
@renovate renovate bot force-pushed the renovate/ckeditor-ckeditor5-react-9.x branch 13 times, most recently from 6bb8a21 to 8e121ca Compare September 18, 2024 17:35
@renovate renovate bot force-pushed the renovate/ckeditor-ckeditor5-react-9.x branch 17 times, most recently from b9331f5 to 83b4945 Compare October 16, 2024 20:18
@renovate renovate bot force-pushed the renovate/ckeditor-ckeditor5-react-9.x branch from 83b4945 to 2711aac Compare October 16, 2024 20:24
Copy link
Contributor Author

renovate bot commented Oct 17, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@shanbady shanbady merged commit 10176b7 into main Oct 17, 2024
11 checks passed
@shanbady shanbady deleted the renovate/ckeditor-ckeditor5-react-9.x branch October 17, 2024 16:01
This was referenced Oct 21, 2024
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.

1 participant