Skip to content

wrong version is considered an update. #6

@matteosister

Description

@matteosister

In my composer.json file, I have

{
    "require": {
        "php": ">=5.3.0",
        "symfony/process": "2.1.*@stable",
        "symfony/filesystem": "2.1.*@stable"
    }
}

why dependency.me tells that there is a 2.3 version available, when so far there is a 2.2beta, and in my composer.json I say that I want the 2.1 branch stable?

the suggested update should take care of the composer.json requirements. If I want 2.1.* 2.2.0 should not be considered an available update, maybe a "new version". an update should be considered if I have 2.1.* in composer, 2.1.7 in the project, and a 2.1.8 (or more) version released.

Here is a link that shows the behavior.

As a side note, branch is mispelled branche in many places. Even in the url. Is this a bug?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions