Make WordPress Core

Opened 3 weeks ago

Last modified 3 weeks ago

#65857 new task (blessed)

Update/Audit NPM Dependencies for 7.2

Reported by: desrosj Owned by:
Priority: normal Milestone: 7.2
Component: Build/Test Tools Version:
Severity: normal Keywords: has-patch
Cc: Focuses:

Description

Previously:

Change History (4)

This ticket was mentioned in PR #12826 on WordPress/wordpress-develop by @sabernhardt.


3 weeks ago
#1

  • Keywords has-patch added

Updates 3 dependencies in Twenty Twenty-Two and Twenty Twenty-Five:

  • @wordpress/browserslist-config from 6.34.0 to 6.52.0
  • cssnano from 7.1.2 to 8.0.2
  • postcss from 8.5.6 to 8.5.25

I ran the following commands in both src\wp-content\themes\twentytwentytwo and src\wp-content\themes\twentytwentyfive:

  1. npm install
  2. npm audit fix
  3. npm dedupe
  4. npm run build

Props: aakashverma1

Trac 65857

Use of AI Tools: none

This ticket was mentioned in PR #12861 on WordPress/wordpress-develop by @desrosj.


3 weeks ago
#2

Updates all devDependency-ies to their latest versions and runs npm audit fix.

Updates are as follows:

  • @playwright/test from 1.61.1 to 1.62.1
  • @types/codemirror from 5.60.17 to 5.60.18
  • @wordpress/e2e-test-utils-playwright from 1.51.0 to 1.52.0
  • @wordpress/prettier-config from 4.51.0 to 4.52.0
  • @wordpress/scripts from 33.0.0 to 34.0.0
  • autoprefixer from 10.5.3 to 10.5.4
  • grunt from 1.6.2 to 1.6.3
  • postcss from 8.5.19 to 8.5.25
  • sass from 1.101.0 to 1.102.0
  • wait-on from 9.0.10 to 9.1.0
  • webpack from 5.108.4 to 5.109.2

Trac ticket: Core-65857.

## Use of AI Tools

None

@sabernhardt commented on PR #12826:


3 weeks ago
#3

In case these themes are updated sooner than WordPress 7.2, I accepted the change to cssnano 7.1.9 and reran the four commands to update package.lock.

However, if the next update is with WordPress 7.2 or later, this pull request probably should be closed and replaced with one that includes other themes.

@wildworks commented on PR #12826:


3 weeks ago
#4

I don't have a strong opinion, but if we are updating the Node version to 24.x in the 7.2 release, we could consider updating the default theme afterwards.

Note: See TracTickets for help on using tickets.