antonioribeiro / antonioribeiro/tracker

minimum-stability:dev fetches older version? is this normal?

Open
#259 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
PHP
Stars
2.9k
Forks
594
PR merge metrics
No merged PRs in 30d

Description

Maybe my understanding of what this does is incorrect.

I always thought that having
```
"minimum-stability": "dev"
```

in your composer.json would basically allow you to get the "bleeding-edge" version of packages. However I just noticed that if I composer require pragmarx/tracker in a fresh Laravel 5.4 installation it adds "pragmarx/tracker": "^3.1" to my composer.json

However if I add the "minimum-stability": "dev" in the composer.json and run the same composer require pragmarx/tracker then it adds "pragmarx/tracker": "^2.1@dev"

Is this right? It sounds wrong to me.. I know this is outside the scope of your project but if you could take a minute to explain why this is happening I would like to know. I tend to use "minimum-stability": "dev" in all my composer.json projects and now I'm worried I may be getting older versions of many other packages as a result

Thanks

Contributor guide

No contributing guide indexed for this repository

Research direction

No repository file, test, or implementation entry point is mentioned. First reproduce the dependency resolution in a fresh Laravel 5.4 project with each composer.json configuration and inspect the resulting package constraints. Done means documenting why minimum-stability: dev selects the reported version, or identifying a reproducible resolution bug.

Written by the indexing model from the issue text.

Assessment

Tech stack
laravel, php
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.