#62220 closed task (blessed) (fixed)
Update/Audit NPM Dependencies for 6.8
| Reported by: | | Owned by: | |
|---|---|---|---|
| Milestone: | 6.8 | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | Build/Test Tools | Keywords: | has-patch |
| Focuses: | Cc: |
Description
Previously:
- #62137 (6.7)
- #61498 (6.6)
- #59658 (6.5)
- #58863 (6.4)
- #57657 (6.3)
- #57535 (6.2)
- #56641 (6.1)
- #54727 (6.0)
- #53361 (5.9)
- #52624 (5.8)
- #51801 (5.7)
- #50769 (5.6)
- #49768 (5.5)
- #49547 (5.4)
- #48203 (5.3)
- #46039 (5.1)
- #45064 (5.0)
- #38199 (4.7)
- #36520 (4.6)
- #35104 (4.5)
- #34177 (4.4)
- #31700 (4.3)
- #31489 (4.2)
- #30141 (4.1)
- #27340 (4.0)
- #26073 (3.9)
Change History (19)
This ticket was mentioned in PR #7996 on WordPress/wordpress-develop by @desrosj.
11 months ago #1
- Keywords has-patch added
@Bernhard Reiter commented on PR #7996:
11 months ago #2
👋 @desrosj Are you planning to land this in the near future (i.e. well before WP 6.8 Beta 1)?
(FWIW, I'd love that, as I have a janitorial PR that requires a package update 😊)
11 months ago #3
@ockham I plan to merge this sometime next week! But it's not a high priority.
Is the concern a merge conflict? Or something else? Don't feel blocked to commit your PR if it's ready and I'll adjust. 😄
@Bernhard Reiter commented on PR #7996:
11 months ago #4
@ockham I plan to merge this sometime next week! But it's not a high priority.
Is the concern a merge conflict? Or something else? Don't feel blocked to commit your PR if it's ready and I'll adjust. 😄
Thank you, but I really can't land mine before a package update 😅 A while ago, I removed some now-obsolete functions from the Navigation block's PHP in Gutenberg. My PR moves -- or rather copies -- them to deprecated.php. But that means that they're colliding with the function declarations that still exist in Core's navigation.php -- until that file is updated by a package sync.
I hope that made sense. But again, not urgent at all -- any time before Beta 1 is fine 😄
11 months ago #6
@ockham Merged in https://core.trac.wordpress.org/changeset/59509!
There are a few other dependencies with updates that need more work in order to be usable (sinon's update causes test failures, for example). But won't get to those for a bit.
@Bernhard Reiter commented on PR #7996:
11 months ago #7
Aaand this is where I realize that this PR was about updating 3rd party dependencies, rather than @wordpress/ packages. In my head, I totally equated "Update NPM packages" with "Sync @wordpress/ NPM packages".
Bonus points for me for never actually checking the diff 🤦♂️
Anyway. Sorry for the noise. Nothing to see here. Carry on.
Unprops @ockham.
11 months ago #8
Sorry! I should have been more specific that it was only devDependencies! No worries!
This ticket was mentioned in PR #8002 on WordPress/wordpress-develop by @desrosj.
11 months ago #9
Trac ticket: https://core.trac.wordpress.org/ticket/62220
This ticket was mentioned in PR #8456 on WordPress/wordpress-develop by @desrosj.
9 months ago #13
Trac ticket: https://core.trac.wordpress.org/ticket/62220
#14
@
9 months ago
- Owner set to desrosj
- Resolution set to fixed
- Status changed from new to closed
In 59929:
This ticket was mentioned in PR #8647 on WordPress/wordpress-develop by @debarghyabanerjee.
8 months ago #18
Trac Ticket: Core-62220
### Summary
This pull request addresses the security vulnerability alert flagged by Dependabot in the npm packages used by the Twenty Twenty theme.
### Changes
- Updated vulnerable npm packages to the latest secure versions
Trac ticket: https://core.trac.wordpress.org/ticket/62220