Adding branch alias to composer.json

[onema]

Adding branch alias to prevent version conflict when using latest master version. See Aliases for more information.

[cordoval]

this is already outdated and should be raised up to 5.4.x-dev

[onema]

Thank you I will update it.

[saturnism]

thanks - we'll look into this.

[saturnism]

@onema btw - is this intended for ppl referring to dev-master version?

[onema]

Sorry I never got back to you.

Yes. This is to prevent issues when you want to use the dev-master version. You would refer to it as 5.4.*@dev

Quoting the composer documentation:

When you are using a VCS repository, you will only get comparable versions for branches that look like versions, such as 2.0 or 2.0.x. For your master branch, you will get a dev-master version. For your bugfix branch, you will get a dev-bugfix version.

If your master branch is used to tag releases of the 1.0 development line, i.e. 1.0.1, 1.0.2, 1.0.3, etc., any package depending on it will probably require version 1.0.*.

If anyone wants to require the latest dev-master, they have a problem: Other packages may require 1.0.*, so requiring that dev version will lead to conflicts, since dev-master does not match the 1.0.* constraint.

See Aliases for more information.

[saturnism]

@onema I'd prefer not to depending on dev-master and should probably choose a version to use.

[onema]

@saturnism It is great that you don't want to depend on dev-master! But If you look at your packagist page, the main section will have you use dev-master.

To prevent this from happening you use a branch alias which will make your master branch semver friendly, take a look at the _google apiclient_ for example:

This is considered a best practice and you should consider adding it to the project.

Take a look at Beau Simens presentation on Composer and semantic versioning for more info.

Also see Composer Stability Flags