What is the version naming convention used by Composer?

The following column composer usage tutorial will explain to you what the version naming convention used by Composer is. I hope it will be helpful to friends in need. !

What version naming convention does Composer use?

Semantic version 2.0.0 used by Composer | Semantic Versioning.

Summary

Version format: Major version number. Minor version number. Revision number. The increment rules of the version number are as follows:

Major version number: when you make incompatible API modifications,

Minor version number: when you make Backwards compatible functionality has been added,

revision number: when you have made backward compatibility bug fixes.

The advance version number and version compilation metadata can be added to the end of "major version number. minor version number. revision number" as an extension.

Introduction

In the field of software management, there is a valley of death called "dependency hell". The larger the system scale, the more packages are added. The more likely you are to find yourself in despair one day.

Releasing new versions of packages on a system with high dependencies can quickly become a nightmare. If the dependencies are too high, you may face the risk of version control being locked (each dependent package must be revised to complete an upgrade). And if the dependencies are too loose, version confusion cannot be avoided (assuming that multiple versions compatible with the future exceed a reasonable number). When the progress of your project is not simple and reliable because of version dependencies or version confusion, it means you are in dependency hell.

The above is the detailed content of What is the version naming convention used by Composer?. For more information, please follow other related articles on the PHP Chinese website!