Skip to content

[FIX] Restore PHP 8.3 compatibility - #2

Merged
Dmi3yy merged 1 commit into
evolution-cms:mainfrom
middleDuckAi:middleDuck/emcp-php83-compat-md
Apr 10, 2026
Merged

[FIX] Restore PHP 8.3 compatibility#2
Dmi3yy merged 1 commit into
evolution-cms:mainfrom
middleDuckAi:middleDuck/emcp-php83-compat-md

Conversation

@middleDuckAi

Copy link
Copy Markdown

Problem

eMCP currently declares PHP 8.4 as the minimum runtime, which blocks installation in PHP 8.3 environments even though the upstream MCP runtime already supports PHP 8.3.

Why

The current package baseline is stricter than both Evolution and the supported laravel/mcp ^0.5.x runtime window. That makes the package harder to adopt as a base Evolution extra without providing any clear code-level benefit.

What Changed

  • lowered the root package requirement from php ^8.4 to php ^8.3
  • pinned the supported upstream runtime to laravel/mcp ^0.5.9
  • updated README and DOCS requirements in English and Ukrainian
  • aligned PRD, SPEC, and upstream-smoke notes with the PHP 8.3 baseline and 0.5.9 minimum
  • updated the existing CI workflow to run on PHP 8.3 instead of 8.4

Where

  • composer.json
  • README.md
  • README.uk.md
  • DOCS.md
  • DOCS.uk.md
  • PRD.md
  • SPEC.md
  • docs/spikes/upstream-smoke.md
  • .github/workflows/ci.yml

Verification

  • composer validate --strict
  • php tests/Phase6/UpstreamAdapterSmokeTest.php
  • php tests/Phase6/DocsConfigCommandsConsistencyTest.php
  • php tests/Phase6/CiWorkflowCoverageTest.php
  • sh scripts/lint-php.sh
  • isolated Composer resolution with platform.php=8.3.0, which resolves successfully and selects laravel/mcp v0.5.9

Remaining Gaps

  • I did not widen the supported upstream window to 0.6.x; this keeps the change minimal and within the current documented ^0.5.x policy
  • no functional runtime behavior changed here; this PR only narrows the package baseline to the already-supported upstream/runtime floor

@Dmi3yy
Dmi3yy merged commit 7bbf5c2 into evolution-cms:main Apr 10, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants