Visitar URL original
[4.x] Prefer stable dependency versions by Hackwar · Pull Request #111 · joomla-framework/filter · GitHub
Skip to content

[4.x] Prefer stable dependency versions - #111

Open
Hackwar wants to merge 1 commit into
joomla-framework:4.x-devfrom
Hackwar:4.x-prefer-stable
Open

Hackwar wants to merge 1 commit into
joomla-framework:4.x-devfrom
Hackwar:4.x-prefer-stable

Conversation

@Hackwar

@Hackwar Hackwar commented Nov 12, 2026

Copy link
Copy Markdown
Contributor

Summary of Changes

composer.json sets "minimum-stability": "dev" without "prefer-stable": true. The package has no committed lock file, so composer update/install (and CI) resolve every dependency that has a development branch to that branch: composer update --dry-run locks phpunit/phpunit 12.5.x-dev, phpstan/phpstan 2.3.x-dev, nikic/php-parser dev-master, myclabs/deep-copy 1.x-dev and about 20 more. joomla/string and joomla/language happen to resolve to 4.0.0 already. With "prefer-stable": true all of them resolve to released versions, while minimum-stability: dev still allows dev branches where nothing stable satisfies a constraint.

Testing Instructions

composer update --dry-run before and after: before, the tools lock to *-dev versions; after, to tagged releases (e.g. phpunit/phpunit 12.5.x releases, phpstan/phpstan 2.3.5). composer validate passes.

Documentation Changes Required

None.

🤖 Generated with Claude Code

composer.json sets "minimum-stability": "dev" without "prefer-stable",
so installing without a lock file resolves PHPUnit, PHPStan and their
dependencies to development branches instead of the released versions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.

1 participant