build(deps-dev): Bump @wordpress/env from 10.39.0 to 11.2.0#394
Merged
build(deps-dev): Bump @wordpress/env from 10.39.0 to 11.2.0#394
Conversation
dependabot
bot
added
dependencies
Bumps [@wordpress/env](https://github.com/WordPress/gutenberg/tree/HEAD/packages/env) from 10.39.0 to 11.2.0. - [Release notes](https://github.com/WordPress/gutenberg/releases) - [Changelog](https://github.com/WordPress/gutenberg/blob/trunk/packages/env/CHANGELOG.md) - [Commits](https://github.com/WordPress/gutenberg/commits/@wordpress/env@11.2.0/packages/env) --- updated-dependencies: - dependency-name: "@wordpress/env" dependency-version: 11.2.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dcalhoun
force-pushed
the
dependabot/npm_and_yarn/wordpress/env-11.2.0
branch
from
5fa2a24 to
6834024
Compare
Enable autoPort in .wp-env.json so wp-env automatically selects an available port, defaulting to 8888 but falling back to an ephemeral port if busy. This allows multiple wp-env instances to run concurrently from different Git working trees. Update bin/wp-env-setup.sh to discover the actual site URL via `wp-env status --json` instead of assuming localhost:8888. CI is unaffected — wp-env forces autoPort off when CI=true. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…script Move the wp-env start call from the Makefile into bin/wp-env-setup.sh so the script controls the full lifecycle. Before starting, it checks wp-env status and skips start if an instance is already running, preventing a second server from being spawned when make wp-env-start is re-run. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…o setup script" This reverts commit bb1941f.
…king trees" This reverts commit 96230ce.
dcalhoun
approved these changes
Mar 23, 2026
Member
dcalhoun
left a comment
dcalhoun
left a comment
There was a problem hiding this comment.
Discarded attempts to support multiple simultaneous wp-envs. This would be helpful when using multiple Git working trees. However, it seems wp-env status currently does not return accurate information for dynamically selected ports. It often returns the information for a server started in a different directory.
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
1 participant
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.
Bumps @wordpress/env from 10.39.0 to 11.2.0.
Changelog
Sourced from
@wordpress/env's changelog.Commits
c20787bchore(release): publishfcfa400Update changelog files8f9faafMerge changes published in the Gutenberg plugin "release/22.8" branch8bfc179chore(release): publishccb148dUpdate changelog files33834c6Merge changes published in the Gutenberg plugin "release/22.7" branch376124achore(release): publishc5b9f23Update changelog files4416c63Merge changes published in the Gutenberg plugin "release/22.6" branchDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)