magento / magento/composer-dependency-version-audit-plugin
Version tag v1.0 is older but higher than any of the other newer tags
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 5
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
The last commit in tag 0.1.0 is 2e846ae from 14 Jun 2021
The last commit in tag 0.1.1 is 2e846ae from 14 Jun 2021
The last commit in tag 0.1.2 is 4ed9b65 on 25 Jun 2021
The last commit in tag v1.0 is 5d75c24 from 13. May 2021
Was tag v1.0 added by accident?
Since composer recognizes is as a stable version and it is considered a higher version than any of the others, maybe it should be removed?
If not, can someone give some insight?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the repository's 0.1.0, 0.1.1, 0.1.2, and v1.0 tags and compare their commit dates and revisions. Then determine from the Composer versioning behavior whether v1.0 was intentional and what repository change, if any, is appropriate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- release
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100