Problem/Motivation
- https://github.com/ckeditor/ckeditor5/releases/tag/v36.0.0
- https://github.com/ckeditor/ckeditor5/releases/tag/v36.0.1
Steps to reproduce
Proposed resolution
- Update
core/package.json cd coreyarn installyarn buildyarn build:ckeditor5-types
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
CKEditor has been updated to 36.0.1
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | 3344083-13-9.5.x.patch | 3.83 MB | longwave |
| #7 | interdiff.txt | 1005 bytes | lauriii |
| #7 | 3344083-7.patch | 3.83 MB | lauriii |
| #6 | Screenshot 2023-03-10 at 12.24.33.png | 46.04 KB | ricardofaria |
| #6 | Screenshot 2023-03-10 at 12.21.46.png | 40.72 KB | ricardofaria |
Comments
Comment #2
longwaveComment #4
ricardofaria commentedFiled for me too. Adding a new patch.
Comment #5
ricardofaria commentedComment #6
ricardofaria commentedI've made new tests locally.
Both patches on #2 and #5 work.
On #5 it is for CK editor 36.0.1.
Comment #7
lauriiiComment #8
wim leersComment #9
wim leersComment #10
longwaveThis looks to fix the test fail from #2, but isn't this just asserting the same thing twice now?
Comment #11
smustgrave commented@longwave I'm reading it as
Is it visible
Is it not empty, guess this could be valid as maybe its visible but empty?
Certainly seems like additional coverage but not sure it's 100% the same thing. Could very well be wrong.
Comment #12
lauriiiI added the
assertNotEmptybefore clicking just to have better error messages in case the button doesn't exist. We could potentially remove the second assertion but I don't see any harm asserting that the button exists after the dropdown tray has been opened. It also makes it clear that we expect three buttons to exist there.Comment #13
longwavePatch for 9.5.x.
Comment #17
catchCommitted/pushed to 10.1.x, cherry-picked to 10.0.x, and committed the 9.5.x patch to 9.5.x, thanks!
Comment #18
wim leersWoah, I did not know this was going to land in Drupal 9.5 & 10.0 too! That's why in #8 I specifically tagged it
10.1.0release notes… 😅I thought our policy was to keep every Drupal core minor on the same CKEditor 5 major, and only update to CKEditor 5 minor/patch releases (which indeed are very rare)?
CKEditor 5 major releases introduce BC breaks. And this is not theoretical, e.g. contrib modules are breaking due to this: #3350252: LinkIt requires new minor version for Drupal 10.1.x, since CKEditor 5 got a major version update (v35 → v36). Contrib modules providing custom CKEditor 5 plugins will often (but not always) have to create a new minor release specifically for the next core minor to chase this. It will often be as simple as re-building using
yarn, but it's still necessary.IMHO we should revert this commit in
9.5.xand10.0.xand unpublish the9.5.6and10.0.6releases, and redo them without this one commit. 😬🙈Comment #20
bradjones1Pretty sure releases can't be unpublished but this may be justification for a narrowly-focused minor version release?
Comment #22
catchI've reverted this. Probably a good idea to put '10.1.x only' in the issue summary for ckeditor major updates.
I don't think we need to unpublish those releases, but we should do new ones. I'm short on time this afternoon so not sure I can get to those today.
Comment #23
catchBack to fixed for 10.1.0
@bradjones1 there's a minor release in June, so it's not long to wait for the new ckeditor5 major.