Make WordPress Core

Opened 19 months ago

Closed 19 months ago

Last modified 19 months ago

#56641 closed enhancement (fixed)

Update/Audit NPM Dependencies for 6.1

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

Description

Previously:

Change History (11)

#1 @desrosj
19 months ago

  • Owner set to desrosj
  • Status changed from new to assigned

[53580] was attached to #55652 instead of this ticket, which follows the practice followed for past releases.

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


19 months ago
#2

  • Keywords has-patch added

#3 @desrosj
19 months ago

In 54294:

Build/Test Tools: Update NPM dependencies in default themes.

This updates NPM dependencies for all default themes that have them.

See #56641.

#4 @desrosj
19 months ago

In 54295:

Build/Test Tools: Update NPM dependencies in default themes, part 2.

Follow up to [54294].

See #56641.

#5 @desrosj
19 months ago

  • Resolution set to fixed
  • Status changed from assigned to closed

In 54296:

Build/Test Tools: Update NPM dependencies to their latest versions.

The following dependencies are being updated:

  • copy-webpack-plugin from 10.2.4 to 11.0.0.
  • dotenv from 16.0.1 to 16.0.2.
  • dotenv-expand from 8.0.3 to 9.0.0.
  • sass from 1.53.0 to 1.55.0.
  • sinon-test from 3.1.3 to 3.1.4.
  • source-map-loader from 3.0.1 to 4.0.0.
  • terser-webpack-plugin from 5.3.1 to 5.3.6.
  • uglify-js from 3.16.1 to 3.17.1.
  • uuid from 8.3.2 to 9.0.0.
  • webpack from 5.72.0 to 5.74.0.

This also contains changes after running npm audit fix.

Fixes #56641.

#6 @milana_cap
19 months ago

  • Keywords add-to-field-guide added

#7 @desrosj
19 months ago

  • Type changed from defect (bug) to enhancement

This ticket was mentioned in Slack in #core by desrosj. View the logs.


19 months ago

#9 follow-up: @desrosj
19 months ago

@milana_cap I think these can be omitted from the field guide. These are just development dependencies. If there are scenarios where updating these dependencies is noteworthy, there would likely be a separate ticket with more discussion and related changes (#56615/#56616 come to mind).

Happy to include them if you feel differently, but there's a lot of other more important and impactful changes we want the developer community to be aware of before these.

#10 in reply to: ↑ 9 @milana_cap
19 months ago

  • Keywords add-to-field-guide removed

Yes, I agree it's not a change users would be interested in. It just occurred to me that we never do documentation for contributors. We do end user and dev docs but those are users.

We never consider contributors, especially if they are not active in this particular release.

Anyway, it was just a thought and perhaps a topic for bigger discussion in future releases.

#11 @desrosj
19 months ago

In 54400:

Build/Test Tools: Update npm dependencies to their latest versions.

This updates the following devDependencies:

  • chalk from 5.0.1 to 5.1.0
  • dotenv from 16.0.2 to 16.0.3
  • sinon from 14.0.0 to 14.0.1
  • uglify-js from 3.17.1 to 3.17.3

This is the final dependency bump for 6.1.

See #56641.

Note: See TracTickets for help on using tickets.