fix: bump version to 3.2.2 to match git tag for Packagist sync#115
Merged
Conversation
Packagist tag sync skipped tag 3.2.2 because composer.json still declared 3.2.1. Bump the version in composer.json and the setup_version in etc/module.xml so they match the published tag. Co-Authored-By: Claude <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
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.
What is the goal?
Fix the failed Packagist tag sync. The sync skipped tag
3.2.2with:The
3.2.2git tag was created whilecomposer.jsonstill declared3.2.1, so Packagist rejected the release.How is it being implemented?
versionincomposer.jsonfrom3.2.1to3.2.2.setup_versioninetc/module.xmlfrom3.2.1to3.2.2to keep it in sync.These are the only two version declarations in the module.
How is it tested?
Automated tests. Version-only change; verified
composer.jsonandetc/module.xmlare the only files declaring the module version.How is it going to be deployed?
master3.2.2tag to the merge commit