


Regarding version number definition and composer dependency version symbols ~, ^
The following is used by composer to introduce the version number definition and composer dependent version symbols~,^, I hope it will be helpful to friends in need!
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 do not Compatible API modifications,
minor version number: when you make a backward compatible functional addition,
revision number: when you make a backward compatible problem correction.
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.
Semantic version 2.0.0 https://semver.org/lang/zh-CN/
~ means that the version number can only change the last paragraph ( If it is ~x.y, the end is y, if it is ~x.y.z, the end is z)
~1.2.3 represents 1.2.3 <= version number< 1.3.0
~1.2 represents 1.2 <= version number<2.0
^ means that in addition to the major version number, the minor version number and patch version number can be changed
^1.2.3 represents 1.2.3 <= version Number < 2.0.0
Special case version number starting with 0:
^0.3.0 equals 0.3.0 <= Version number <0.4.0 Note: not <1.0 .0
Because: The rule of semantic versioning is that if the major version number starts with 0, it means that it is an unstable version (unstable). If it is in an unstable state, the minor version number is not allowed to be backward compatible.
So if you want to specify a library starting with 0, you must pay attention:
Dangerous writing: ~0.1 equals 0.1.0 <= version number<1.0.0
Insurance writing method: ^0.1 equals 0.1.0 <= Version number <0.2.0
For more composer-related technical articles, please visit the composer column: https://www.php.cn /tool/composer/
The above is the detailed content of Regarding version number definition and composer dependency version symbols ~, ^. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



I encountered a tricky problem when developing a new Laravel project: how to quickly build a fully functional and easy-to-manage content management system (CMS). I tried multiple solutions, but all gave up because of complex configuration and inconvenient maintenance. Until I discovered the LaravelCMS package mki-labs/espresso, which not only simple to install, but also provides powerful functions and intuitive management interface, which completely solved my problem.

In project development, it is often necessary to create command-line tools to simplify daily tasks or automate processes. However, creating a command line interface that is beautiful and easy to test is not easy. Recently, I encountered this problem while developing a project that requires command line tools. After some exploration, I found the Symfony/Console library, which greatly simplifies the creation process of command line interfaces.

I encountered a common but tricky problem when developing a large PHP project: how to effectively manage and inject dependencies. Initially, I tried using global variables and manual injection, but this not only increased the complexity of the code, it also easily led to errors. Finally, I successfully solved this problem by using the PSR-11 container interface and with the power of Composer.

When developing Yii framework projects, you often encounter situations where you need to obtain a large amount of data from the database. If appropriate measures are not taken, directly obtaining all data may cause memory overflow and affect program performance. Recently, when I was dealing with a project on a large e-commerce platform, I encountered this problem. After some research and trial, I finally solved the problem through the extension library of pavle/yii-batch-result.

During development, HTTP requests are often required, which may be to get data, send data, or interact with external APIs. However, when faced with complex network environments and changing request requirements, how to efficiently handle HTTP requests becomes a challenge. I have encountered a problem in a project: I need to send requests to different APIs frequently, and log the requests to facilitate subsequent debugging and analysis. After trying several methods, I discovered the yiche/http library. It not only simplifies the processing of HTTP requests, but also provides dynamic logging functions, greatly improving development efficiency.

When developing websites using CraftCMS, you often encounter resource file caching problems, especially when you frequently update CSS and JavaScript files, old versions of files may still be cached by the browser, causing users to not see the latest changes in time. This problem not only affects the user experience, but also increases the difficulty of development and debugging. Recently, I encountered similar troubles in my project, and after some exploration, I found the plugin wiejeben/craft-laravel-mix, which perfectly solved my caching problem.

When developing a government website project, I encountered a difficult problem: how to improve the accessibility of the website to meet the needs of different users, especially for visually impaired users, navigating and operating the website can be very difficult. After trying multiple methods, I found a JavaScript library called FlyingFocus that significantly improves the accessibility of the website. However, integrating it into the SilverStripe website is a challenge. Fortunately, I found the dia-nz/silverstripe-flying-focus module, which simplified the integration process of FlyingFocus and solved my puzzle.

I'm having a tough problem when developing a complex web application: how to effectively handle JavaScript errors and log them. I tried several methods, but none of them could meet my needs until I discovered the library dvasilenko/alterego_tools. I easily solved this problem through the installation of this library through Composer and greatly improved the maintainability and stability of the project. Composer can be learned through the following address: Learning address
