Repository navigation
chore(composer): remove stale dev-main branch alias - #10
Merged
Merged
Conversation
The alias mapped dev-main to 1.x-dev. Since v2.0.0 was tagged, main carries the 2.x line while still declaring itself as 1.x — a project requiring ^1.0 with dev stability allowed would resolve main's 2.x code as if it were 1.x. Removing the alias rather than bumping it to 2.x-dev: an alias only matters when something consumes the dev branch, and it then has to be maintained at every major, which is exactly what failed here. No internal consumer requires dev-main — all four of them pin tags (^1.0, ^1.0.3). Consumers of dev-main, if any appear later, can require dev-main explicitly; that works without an alias. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
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.
Problème
composer.jsondéclarait :Depuis le tag
v2.0.0,mainporte la ligne 2.x mais continue à se déclarer1.x-dev. Conséquence : un projet en^1.0qui accepte le dev (minimum-stability: dev) résoudrait le code 2.x demaincomme s'il était du 1.x. L'alias ment.L'alias périmé s'est même retrouvé figé dans les métadonnées du tag
v2.0.0— inoffensif, unbranch-aliasne s'appliquant qu'aux branches, mais ça confirme que la release ne l'a pas touché.Pourquoi supprimer plutôt que bumper en
2.x-devUn alias de branche n'a d'utilité que si quelque chose consomme la branche de dev — et il doit alors être maintenu à chaque majeure, ce qui vient d'échouer.
Aucun consommateur connu ne requiert
dev-main: tous épinglent des tags. Si un consommateur de la branche apparaît plus tard, il peut requérirdev-mainexplicitement, ce qui fonctionne sans alias.Impact
^1.0,^2.0).dev-mainreste installable sous son nom réel, et n'est plus matché par une contrainte^1.x.composer validate: OK.🤖 Generated with Claude Code