chore: allow utopia-php/console 0.2

[loks0n]

Summary

• Widen utopia-php/console from 0.1.* to ^0.1 || ^0.2.
• console 0.2 only adds Utopia\Command and keeps the whole 0.1 Console surface this library uses (three call sites in src/), so accepting both lines lets consumers upgrade independently instead of forcing every 0.1 consumer to move at once.
• composer.lock changes by content hash only; resolved versions are unchanged.

Appwrite is moving to console 0.2 for structured command execution and currently has to alias 0.2.9 as 0.1.1 because of this pin.

Supersedes #882, which hard-bumps to 0.2.* from a base that predates the cache 5 and validators 1.0 bumps.

Testing

• composer update --lock (no version changes)
• CI adapter matrix

🤖 Generated with Claude Code

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 60f9f3c0-a8dd-4990-b448-a62df7e07650

📥 Commits

Reviewing files that changed from the base of the PR and between 5592a23 and f4503d5.

⛔ Files ignored due to path filters (1)

• composer.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• composer.json

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The Composer dependency constraint for utopia-php/console now permits both 0.1.x and 0.2.x releases.

Changes

Console dependency compatibility

Layer / File(s)	Summary
Update console version constraint composer.json	The utopia-php/console requirement accepts 0.1.* and 0.2.* releases.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: abnegate

Merge Risk: ⚪ Minimal · up to f4503

The constraint now permits console 0.2.x while preserving existing 0.1.x installs, allowing consumers to upgrade independently. No concrete production-impacting risk remains.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: allowing the project to use utopia-php/console version 0.2 while retaining the existing 0.1 constraint.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/allow-console-0.2

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Confidence Score: 5/5

The dependency constraint change appears safe to merge, although console 0.2 still lacks the previously requested behavioral test coverage.

Findings

1.  Console 0.2 remains untested ▶

Fix with agent prompt

### Issue 1
composer.json:undefined-42
The newly supported `0.2.*` line is not exercised by CI because the existing jobs install the lock file, which still resolves `utopia-php/console` 0.1.1. This means regressions in the `Console::warning()` and `Console::error()` behavior used by this library could pass unnoticed. Add a behavioral CI job that resolves console 0.2 and runs the normal test suite rather than asserting the version constraint itself.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

• Changes the console constraint to ^0.1 || ^0.2.
• Regenerates the Composer lock-file content hash without changing resolved packages.
• The previously reported lack of behavioral test coverage for console 0.2 remains outstanding.

_{Reviews (2) · Last reviewed commit: "chore: allow utopia-php/console 0.2"}

[greptile-apps]

Console 0.2 remains untested

The newly supported 0.2.* line is not exercised by CI because the existing jobs install the lock file, which still resolves utopia-php/console 0.1.1. This means regressions in the Console::warning() and Console::error() behavior used by this library could pass unnoticed. Add a behavioral CI job that resolves console 0.2 and runs the normal test suite rather than asserting the version constraint itself.

Prompt To Fix With AI

This is a comment left during a code review.
Path: composer.json
Line: 42

Comment:
**Console 0.2 remains untested**

The newly supported `0.2.*` line is not exercised by CI because the existing jobs install the lock file, which still resolves `utopia-php/console` 0.1.1. This means regressions in the `Console::warning()` and `Console::error()` behavior used by this library could pass unnoticed. Add a behavioral CI job that resolves console 0.2 and runs the normal test suite rather than asserting the version constraint itself.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.