Composer and stable version



  • I'm taking a little package. github (formed packagistafter the issuance of the release 2.0.0 - he showed him as stable. Then, I found a serious mistake in the implementation, and as far as I understand the version system, since API didn't change, after the comm created a release. 2.0.1 (i.e. corrections not affecting API), but packagist That's how it feels. 2.0.0 stable. How do you translate it into a new version?

    UPDATE:

    {
        "name": "name/name",
        "description": "Desctiption",
        "authors": [
            {
                "name": "AuthorName",
                "email": "email@gmail.com"
            }
        ],
        "license": "MIT",
        "require": {
            "php": ">=5.3.0"
        },
        "require-dev": {
            "phpunit/phpunit": "4.7.*",
            "satooshi/php-coveralls": "dev-master"
        },
        "autoload": {
            "psr-4" : {
                "NameSpace\\" : "src/"
            }
        }
    }
    


  • composer.jsongithub May I add version: "2.0.1" and another new strategy v2.0.1♪ Here. packagist There's a button to update the information.

    UPD

    So you can create a new branch. 2.0 in which to maintain the rights of the Minor Version and Packagist They'll get caught. https://getcomposer.org/doc/02-libraries.md#specifying-the-version for composer

    UPD 2

    On instructions @Etki, it turns out composer.json It's really better not to tell the story. https://getcomposer.org/doc/04-schema.md#version

    Accordingly, the addition of the current and/or branches with the version will be sufficient.

    UPD 3

    Turns out the problem was on the side. https://poser.pugx.org the one that put information on the package.




Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2