Problem/Motivation
https://github.com/ckeditor/ckeditor5/releases/tag/v43.3.1
Steps to reproduce
Proposed resolution
Remaining tasks
Backport this to the gazillion current branches, TBD by the core committers.
User interface changes
Introduced terminology
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|
Issue fork drupal-3487579
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
spokjeUpdated
@ckeditor/*,ckeditor5andwebpackto their latest releases.Comment #4
spokjeComment #5
spokjeMirroring status of parent issue, which became critical.
Comment #6
smustgrave commentedDo we add test coverage for new features added?
Comment #7
spokjeAFAICT we never did with previous bumps. although the idea is not without its merits.
I fear however, if we did, we'd be about just finished with defining and implementing the tests when a new version comes out.
Anyway: n=1, mileage may vary, yada yada.
Comment #8
smustgrave commentedThe one I was curious about was 43.3.0 with media-embed but now realize we don't have that button lol.
Applied the update locally at least and ckeditor seems to behave as expected.
Comment #12
catchCommitted/pushed to 11.x and 11.1.x, thanks!
We should backport this to 10.5.x/10.4.x so moving there.
Comment #15
spokjeComment #16
smustgrave commentedSeems like a good re-roll for 10.5
Comment #17
catchI'm getting errors from commit-code.sh trying to commit this locally.
yarn check -s says:
This might be just an issue with my local so leaving RTBC.
Comment #18
spokjeSame happens here. I think it has something to do with the fact I mistakenly started with a
$ $ yarn upgrade-interactive, ehich is more/only for yarn 4.xLet's start with a new MR.
Comment #21
spokjeWell, that required a lot more elbow grease than I expected/needed, but the errors are gone.
Comment #22
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #23
spokjeNo, bad bot!
Comment #24
spokjeComment #25
nod_hang on, yarn vendor-update was not run on 11.x, lots of new languages were added. So we're missing translation files
Comment #26
spokjeyarn build was run on 11.x here:
https://git.drupalcode.org/project/drupal/-/merge_requests/10190/diffs?c...
yarn buildincludesyarn vendor-update.So I'm confused now, what files are missing and do they turn up when you do a
yarn buildon11.x?Do the turn up if you do a
yarn vendor-updateon11.x?If the first question is answered with a yes, I messed it up.
Anything else, I'm scratching my head.
Comment #27
spokjeDiscussed this with @nod_ in Slack, and, of course he was right.
Adding an MR with the MIA files now.
Comment #29
spokjeOpened MR!10246 to add the missing JS files to
11.x, hoping that it's a 1-on-1 backport to11.1.x.I've changed my local, faulty
.gitignoreso this won't happen again.All credits for finding out about this distaster-in-progress to @nod_!
Comment #32
spokjeAdded missing files to the
10.5.xMR, but that branch seems to have a broken HEAD: https://www.drupal.org/project/drupal/issues/3488179#comment-15863742Comment #34
nod_Thanks!
Comment #35
spokjeHEAD unbroken, rebased
Comment #36
smustgrave commentedRebase seems good on 10.5.x now.
Comment #40
catchCommitted/pushed to 10.5.x and cherry-picked to 10.4.x, thanks!
I'm leaving this open for discussion about whether we want to try to update 10.3.x too - it might make things easier if there's a ckeditor5 security release in the next six months, if the update is otherwise non-disruptive.
Comment #41
longwaveI don't think we should, just because there were no breaking changes in v42 or v43 that affected core doesn't mean that contrib or custom plugins won't be affected.
Comment #42
longwave