Fixed
Project:
Drupal core
Version:
11.4.x-dev
Component:
other
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
30 Jun 2026 at 02:06 UTC
Updated:
24 Jul 2026 at 03:18 UTC
Jump to comment: Most recent
Why is cspell running on composer/Metapackage/CoreRecommended/composer.json
https://git.drupalcode.org/project/drupal/-/jobs/10633584#L65
Ignore composer.json and composer.lock files.
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 #2
quietone commentedBecause it has a description field that is English text.
Comment #3
quietone commentedBut I take your point. I would think we can get a one line description correct.
Comment #4
mstrelan commentedThe problem here is that bumping one of core's dependencies introduced a new transient dependency on
symfony/polyfill-deepclone, and cspell doesn't like the word "deepclone". You could argue that cspell helped us to notice a new dependency was added, but of course that wouldn't happen if the new dependency was a dictionary word. You could also argue that since we're adding deepclone as a dependency, this is a good prompt to tell us we might want to put it in the dictionary, as we might refer to it in other places.On the other hand, it felt frustrating that this interrupted my workflow, and I'm not sure it was worthwhile.
TL;DR this should be up for discussion rather than just a matter of just excluding this file from cspell to make it easier.
Comment #5
longwave+1 - looks like we could remove various other non-words from dictionary.txt if we do this such as "colinodell", "spaze", "lullabot" etc.
Given that composer.json is mostly machine readable except for "description" and maybe one or two other keys, to me means any disruption caused outweighs any benefits here.
Comment #7
mstrelan commentedUpdated config and dictionaries. LLM assisted here to identify what we could remove. Only two words were removable due to excluding composer.json, the others were already removable. Have used separate commits to highlight which ones are due to this config change.
Comment #8
longwaveAdded a question.
Comment #9
mstrelan commentedAdded glob pattern
Comment #10
smustgrave commentedSeems feedback from @longwave has been applied.
Random looking at the list seems maybe the dictionary.txt has gotten behind, example lzma was removed but wasn't in composer.json. Almost wonder if there's a weekly job that could be ran to check that? Not in scope here obviously just thinking out loud.
Comment #12
catchCommitted/pushed to main, thanks! Also cherry-picked to 11.x and 11.4.x
Comment #17
godotislateThis broke 11.x and 11.4.x because Drupal\Core\Archiver\Tar, which was removed in main, has usages of
lzma.See
https://git.drupalcode.org/project/drupal/-/jobs/11120775
https://git.drupalcode.org/project/drupal/-/jobs/11120802
Comment #19
godotislatehttps://git.drupalcode.org/project/drupal/-/merge_requests/16415
Comment #20
xjmCame here to say that instead of not-spellchecking
composer.json, I thought the correct approach was adding project names to the relevant dictionary. But it looks like in this case the backport did not match what was needed for those branches, correct?The 11.x pipeline is indeed green now on the MR, so RTBCing. I looked for 11.4.x on the pipeline daily/weekly jobs, but it is maybe running only on commit? Which might be more resource-efficient anyway given the rate of backports, but earlier release branches have daily or weekly jobs. I did find this 11.4.x job and confirmed the fail there is also:
Thus, this should fix 11.4.x as well.
Comment #21
mstrelan commentedIMHO we should just spellcheck on main and skip for backport branches.
Comment #22
acbramley commentedAhh didn't realise this issue was still open, I created #3612912: Spellcheck is failing on 11.x for the 11.x failure. Can we get that committed? Either here or in the other issue :)
Comment #23
catchCommitted/pushed to 11.x and 11.4.x, thanks!
We could probably take a similar approach for cspell to the one in #3580398: Skip on-commit jobs for the main and 11.x branches (in reverse), would save a few thousand CI minutes every year probably.
Comment #28
mstrelan commentedOpened #3612933: Only run cspell on main and MRs that target main as a follow up