You have tagged this as version 2.6.1; however, you neglected or forgot to update the composer.json property value itself to 2.6.1. This means packagist.org may not see the latest version as 2.6.1 or may be disseminating 2.6.1 as version 2.6.0.
The real solution is to create a GitHub workflow to automatically update the composer.json "version" key when a new tag is created. This way the tagged release will have a fixed version matching the tag version.
martin-cod
commented
4 months ago
You have tagged this as version 2.6.1; however, you neglected or forgot to update the composer.json property value itself to 2.6.1. This means packagist.org may not see the latest version as
2.6.1or may be disseminating2.6.1as version2.6.0.The real solution is to create a GitHub workflow to automatically update the composer.json "version" key when a new tag is created. This way the tagged release will have a fixed version matching the tag version.