fix: remove hardcoded version from composer.json#94
Merged
tdwesten merged 1 commit intotdwesten:mainfrom Mar 31, 2026
Merged
Conversation
Owner
|
Oh, thanks! I have learned something today. Thanks, @kgirzadas! |
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
2 participants
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.
Problem
The
composer.jsonfile had a hardcoded"version": "v3.0.0"field.When Packagist crawls a git tag (e.g. v3.0.1), it reads
composer.jsonat that tag. If the declared version doesn't match the tag name, Packagist
either skips the tag or registers it under the wrong version — which is why
releases v3.0.1–v3.0.5 don't appear on Packagist.
Fix
Removed the
"version"field. Composer/Packagist automatically derivesthe version from the git tag name — this field should never be hardcoded
in a library's composer.json.
Impact
by Packagist and installable via Composer.