Move all packages from require to require-dev to avoid conflicts on installation#144
Merged
joetannenbaum merged 2 commits intomainfrom Apr 20, 2026
Merged
Move all packages from require to require-dev to avoid conflicts on installation#144joetannenbaum merged 2 commits intomainfrom
require to require-dev to avoid conflicts on installation#144joetannenbaum merged 2 commits intomainfrom
Conversation
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.
Since the CLI is shipped as a self-contained PHAR, the runtime deps in
requirewere just conflict surface for anyone runningcomposer global require laravel/cloud-cli, a pinnedilluminate/*in another global package would block the install even though the PHAR doesn't need the outer vendor at all. Moved everything exceptphp: ^8.2torequire-devso global installs have nothing left to collide with.Also added a smoke test to
release.shthat runs the freshly-built PHAR before the commit/push: checks the file exists, that--versionmatches the tag we just built, and thatlistboots cleanly (which exercises most bundled deps). Any failure aborts before anything is pushed or released.