chore: Remove hardcoded version field from composer.json - #31
Merged
Conversation
Composer recommends omitting the version property and inferring it from VCS tags instead — a hardcoded value silently drifts from the real tagged release the next time this package is tagged without remembering to also bump this field.
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.
Composer recommends omitting
versionand inferring it from VCS tags — a hardcoded value silently drifts from the real tagged release. Flagged during a fleet-wide Packagist packages audit.Test plan
composer validate --strictpassescomposer update --lock— no security advisories, lock hash refreshed