Repository navigation
Use npm-native Node runtime enforcement - #578
Merged
leopiccionia merged 7 commits intoJun 2, 2026
Merged
Conversation
Add the stable PHPCompatibilityWP PHPCS standard as a Composer dev dependency and configure a dedicated compatibility ruleset for the JEO source tree. Replace the repository-owned PHP compatibility script and parser matrix with a PHPCompatibilityWP workflow job configured for the PHP 8.0-8.5 support window. Remove the custom compatibility script and align README and maintenance documentation so static PHP compatibility is owned by PHPCompatibilityWP while runtime coverage remains with the WordPress smoke workflow. Closes InfoAmazonia#524. Co-authored-by: Codex <codex@openai.com>
This was referenced May 21, 2026
bwstefano
force-pushed
the
codex/npm-native-node-runtime
branch
from
May 21, 2026 18:13
cbb2520 to
876b3f5
Compare
Co-authored-by: Codex <codex@openai.com>
Co-authored-by: Codex <codex@openai.com>
Co-authored-by: Codex <codex@openai.com>
bwstefano
force-pushed
the
codex/npm-native-node-runtime
branch
from
May 21, 2026 18:55
876b3f5 to
6363762
Compare
Update the WordPress 7.0 smoke-test documentation to preserve the PHPCompatibilityWP wording introduced by the PHP compatibility PR. This keeps the all-PR integration order from conflicting while still documenting the new WordPress smoke matrix. Co-authored-by: Codex <codex@openai.com>
…ordpress-smoke # Conflicts: # README.md # docs/dev/php-compatibility.md
…node-runtime # Conflicts: # docs/dev/dependency-upgrade-smoke-tests.md
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
2 participants
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.
Summary
This PR removes the custom Node version preflight and lets npm enforce the supported runtime through versioned project metadata.
Changes
scripts/check-node-version.mjs,check:env, and thepreinstallhook..npmrcwithengine-strict=true.devEnginesalongside the existingenginespolicy for Node 24 and npm 10+.npm run check:envsteps from CI and release workflows.Dependency
This PR should be merged after #577. The branch intentionally includes the resolved #577 history so the dependency-maintenance checklist keeps the PHPCompatibilityWP wording from #576/#577 while removing the obsolete
npm run check:envstep from this PR.Once the earlier PRs are merged into
develop, this PR can be updated/rebased and its visible diff should collapse back to the npm-native runtime changes.Validation
git diff --check upstream/develop..codex/npm-native-node-runtimenpm ci, build, tests, PHP checks, and WordPress smoke.