Repository navigation
build(deps): combine eight Dependabot updates - #23
Merged
Merged
Conversation
aryanjasala
approved these changes
Oct 1, 2026
This was referenced Oct 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does
Applies eight Dependabot updates in one change, so they land together without lockfile conflicts. Each version and commit is exactly what the Dependabot PR proposed.
@wordpress/env11.7.0 to 11.16.0dotenv17.4.2 to 18.0.4axios1.18.1 to 1.20.0 (transitive, lockfile only)@wordpress/blocks15.25.0 to 16.1.0@wordpress/block-editor16.1.0 to 18.0.0@rtcamp/eslint-configc5f84e6tob37138f@rtcamp/wp-tooling18d003cto119e078actions/deploy-pagesv4 to v5.0.1#9 and #14 go in together on purpose: on its own, either one installs two copies of
@wordpress/blocks.Dependabot closes each PR above once this merges, because the new versions are then on
main.Not included
@babel/core8: the WordPress toolchain is still on Babel 7, so Jest, the build and lint fail.wp-cli/i18n-command3: it needs an unreleased WP-CLI 3.@wordpress/scripts36:test-unit-jsnow runs Vitest, which needs a separate change.How I verified
Node 22.19, on top of
mainat6fc0712:npm cileaves the lockfile unchanged, andnpm install --package-lock-onlyreports it up to date.lint:js,lint:cssandlint:package-jsonpass. Jest passes 19 of 19.build:prodpasses, andassets/buildis byte-identical tomain.start:assetsandstart:blocksread their ports from.env.localwith dotenv 18.wp-tooling validatepasses for all 46 scaffolds, and a generated post type usesrtCamp\WPPrimitives\.deploy-pagesv5 stays untested here until GitHub Pages is enabled for this repository.