Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
Update stylelint to the latest version and fix a single CSS regression.
Needed so no warnings when installing stylelint-order - see #3024527: Add and configure stylelint-order
Proposed resolution
Do it.
Remaining tasks
User interface changes
None
API changes
None
Data model changes
None
Release notes snippet
Stylelint has been updated from 9.1.1 to 9.10.1
Comment | File | Size | Author |
---|---|---|---|
#8 | 3038562-2-8.patch | 34.4 KB | alexpott |
#8 | 2-8-interdiff.txt | 27.28 KB | alexpott |
#6 | 3038562-4.patch | 133.92 KB | markconroy |
#2 | 3038562-2.patch | 52.67 KB | alexpott |
Comments
Comment #2
alexpottComment #3
alexpottThe yarn.lock was updated by doing
yarn upgrade stylelint
Comment #6
markconroy CreditAttribution: markconroy as a volunteer and at Annertech commentedHi @alexpott
This looks good to me. I wonder would it be worth increasing the version in package.json to 9.10.1 to reflect this, or are we okay just having it in the yarn.lock file?
Just in case, here's a patch with the package.json updated and the
yarn run lint:css --fix
ran, with the same results.I'll mark this RTBC in either case.
Comment #7
alexpott@markconroy something else has happened on your yarn update - a load of integrity stuff has changed. Making interdiffs and checking what's happening helps. Maybe you are not on the latest yarn or something - I'm on 1.13.0
Comment #8
alexpottFor some reason it's update less again /shrug javascript package management.
Comment #11
lauriiiConfirmed manually that updating stylelint doesn't cause any new coding standard violations.
Committed c73c894 and pushed to 8.8.x. Patch- and minor-level library updates are allowed to be backported before RC phase, so I backported this to 8.7.x as well. Thanks!
Comment #13
xjmWe're still in commit freeze, so reverted from 8.7.x for now.
Comment #15
lauriiiCherry-picked again now that the commit freeze is over. 😇
Comment #16
xjmComment #17
xjmMissing a CR I think.
Comment #18
alexpottDo we really need a CR? This is a JS dev dependency and it's not a major version update? Also it doesn't affect the rules or how they are run at all. I.e. the change record has no change to report. The CSS change was due to a patch being committed that didn't comply with the current ruleset.
Comment #19
xjmWe generally add CRs for all minor dependency updates AFAIK. Just because we don't know of any disruptive changes, that doesn't mean someone downstream using the library we provide isn't impacted.
Comment #20
xjmOr in other terms, not having CRs for dependency updates causes extra work to find the updates, so let's just add CRs each time. We add CRs for way less impactful things.