Support utopia-php/http 2.x

[loks0n]

Summary

• Bump utopia-php/http constraint to ^2.0@RC so 2.0.0-rc1 (and future RCs / stable 2.x) resolve.
• Update composer.lock accordingly.

Test plan

• composer install resolves cleanly
• composer test passes against http 2.0.0-rc1

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

This PR bumps utopia-php/http from the pinned 0.34.25 to ^2.0@RC, resolving to 2.0.0-rc1 in the lock file. The consuming code in Platform.php uses Http::init(), Http::addRoute(), and Route—these APIs should be verified against the 2.x changelog to confirm no breaking changes apply.

• The ^2.0@RC constraint in a library's composer.json can prevent installation for downstream consumers whose root package uses \"minimum-stability\": \"stable\" (the Composer default), because stability flags in a library are not promoted to the root resolution context. Until a stable 2.0.0 is tagged, any consumer without their own @RC flag or a relaxed minimum-stability will get a resolution failure.

Confidence Score: 3/5

Not safe to merge until the downstream installability impact of the RC constraint is addressed or a stable 2.0.0 ships.

A P1 finding is present: as a library, shipping a ^2.0@RC require constraint actively breaks installation for any downstream consumer with the default minimum-stability: stable, since no stable 2.x release exists yet.

composer.json — the RC stability constraint on a library dependency

Important Files Changed

Filename	Overview
composer.json	Bumps utopia-php/http to ^2.0@RC; RC constraint in a library can break downstream consumers with minimum-stability: stable until a stable 2.x is released
composer.lock	Lock file updated to utopia-php/http 2.0.0-rc1 with correct stability-flags entry (RC=5); content-hash and references are consistent

_{Reviews (1): Last reviewed commit: "Bump utopia-php/http to 2.0.0-rc1" | Re-trigger Greptile}

[greptile-apps]

RC constraint in a library breaks downstream consumers

Because utopia-php/platform is a "type": "library", the ^2.0@RC constraint gets evaluated in the context of each downstream consumer's root package. A consumer with "minimum-stability": "stable" (the default) will fail to resolve this dependency entirely until a stable 2.0.0 release exists — Composer won't install 2.0.0-rc1 for them even though this library explicitly allows it, because stability flags in a library's own composer.json are ignored at dependency-resolution time for root packages with stricter stability settings.