blocks|key|1904656|text|答案是：Tags。如果你不想使用标签，你也可以使用Alias。但值得一提的是，您应该只在包稳定时才将其标记为稳定，而不是让其他人相信它们是稳定的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1904657|更新:更多链接：Stability|1904658|entityMap|0|LINK|mutability|MUTABLE|url|http://getcomposer.org/doc/02-libraries.md#tags|1|http://getcomposer.org/doc/articles/aliases.md|2|https://getcomposer.org/doc/articles/versions.md#stability^0|4|4|0|P|5|1|0|8|9|2|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]|$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]]]

The answer is: <a href="http://getcomposer.org/doc/02-libraries.md#tags">Tags</a>. Your may also use <a href="http://getcomposer.org/doc/articles/aliases.md">Alias</a>, if you don't want to use tags. But it's worth to mention, that you should only mark your packages as stable, when they are stable and not to make others believe they are.

Update: One more link: <a href="https://getcomposer.org/doc/articles/versions.md#stability">Stability</a>

blocks|key|1904714|text|详细阐述KingCrunch的答案，因为这对我来说并不是很明显。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1904715|来自https://getcomposer.org/doc/02-libraries.md#specifying-the-version|offset|length|1904716|1904717|当你在Packagist上发布你的包时，它能够从VCS+(git，svn，hg)信息推断出版本。这意味着您不必显式地声明它。|blockquote|1904718|1904719|1904720|这在Github中非常简单：https://help.github.com/articles/working-with-tags/|1904721|此外：|1904722|1904723|如果您正在手动创建包，并且确实需要显式指定，则只需添加一个版本字段：|1904724|1904725|{+"version"："1.0.0“}|1904726|entityMap|0|LINK|mutability|MUTABLE|url|https://getcomposer.org/doc/02-libraries.md#specifying-the-version|1|https://help.github.com/articles/working-with-tags/^0|0|2|1U|0|0|0|0|0|0|E|1F|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@]|9|@$D|17|E|18|1|19]]|A|$]]|$1|F|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|G|3|H|5|I|7|1B|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1E|8|@]|9|@$D|1F|E|1G|1|1H]]|A|$]]|$1|N|3|O|5|6|7|1I|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|Q|3|R|5|I|7|1K|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1M|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]]|W|$X|$5|Y|Z|10|A|$11|12]]|13|$5|Y|Z|10|A|$11|14]]]]

Elaborating on KingCrunch's answer, since this was not immediately obvious to me.

From <a href="https://getcomposer.org/doc/02-libraries.md#specifying-the-version" rel="nofollow">https://getcomposer.org/doc/02-libraries.md#specifying-the-version</a>

<blockquote>
 When you publish your package on Packagist, it is able to infer the version from the VCS (git, svn, hg) information. This means you don't have to explicitly declare it.
</blockquote>

This is very easy with Github:
<a href="https://help.github.com/articles/working-with-tags/" rel="nofollow">https://help.github.com/articles/working-with-tags/</a>

Furthermore:

<blockquote>
 If you are creating packages by hand and really have to specify it
 explicitly, you can just add a version field:

<pre><code>{
 "version": "1.0.0" 
}
</code></pre>
</blockquote>

blocks|key|2006034|text|要回答这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2006035|是dev-master|offset|length|style|CODE|2006036|for+packagist，是*@stable|unordered-list-item|2006037|
，是|2006038|2006039|2006040|2006041|有关“稳定”或“冻结”作曲家版本的更多信息|2006042|冻结使其稳定|2006043|获取需求的最新版本有时很有用，尤其是在审计期间，这就是为什么我制作了一个composer包来稳定所有依赖项：Composer+Stable+Versions+(https://github.com/MaximeCulea/Composer-Stable-Versions)。|2006044|使用此命令，您对composer.json的依赖关系将自动从：|2006045|"wpackagist-plugin/wordpress-seo":"6.2"|2006046|进入：|2006047|"wpackagist-plugin/wordpress-seo":"*@stable"|2006048|冻结编写器版本|2006049|如果之后你打算做相反的事情来获取你测试网站时使用的composer.lock的最新版本，看看我的另一个composer命令：Composer+Freeze+Versions+(https://github.com/MaximeCulea/Composer-Freeze-Versions)。|2006050|使用此命令，您对composer.json的依赖关系将自动锁定：|2006051|"wpackagist-plugin/wordpress-seo":"@stable"|2006052|2006053|2006054|2006055|希望能有所帮助。|2006056|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/MaximeCulea/Composer-Stable-Versions|1|2|https://github.com/MaximeCulea/Composer-Freeze-Versions|3^0|0|1|A|0|F|8|0|0|0|0|0|0|0|1I|O|0|28|1J|1|0|0|0|13|0|0|0|18|0|0|1Q|O|2|2G|1J|3|0|0|0|17|0|0|0|13|0|0|0^^$0|@$1|2|3|4|5|6|7|1S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1T|8|@$D|1U|E|1V|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|1W|8|@$D|1X|E|1Y|F|G]]|9|@]|A|$]]|$1|K|3|L|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|M|3|-4|5|J|7|20|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|21|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|22|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|23|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|24|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|25|8|@]|9|@$D|26|E|27|1|28]|$D|29|E|2A|1|2B]]|A|$]]|$1|V|3|W|5|6|7|2C|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|2D|8|@$D|2E|E|2F|F|G]]|9|@]|A|$]]|$1|Z|3|10|5|6|7|2G|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|2H|8|@$D|2I|E|2J|F|G]]|9|@]|A|$]]|$1|13|3|14|5|6|7|2K|8|@]|9|@]|A|$]]|$1|15|3|16|5|6|7|2L|8|@]|9|@$D|2M|E|2N|1|2O]|$D|2P|E|2Q|1|2R]]|A|$]]|$1|17|3|18|5|6|7|2S|8|@]|9|@]|A|$]]|$1|19|3|1A|5|6|7|2T|8|@$D|2U|E|2V|F|G]]|9|@]|A|$]]|$1|1B|3|10|5|6|7|2W|8|@]|9|@]|A|$]]|$1|1C|3|Y|5|6|7|2X|8|@$D|2Y|E|2Z|F|G]]|9|@]|A|$]]|$1|1D|3|-4|5|6|7|30|8|@]|9|@]|A|$]]|$1|1E|3|1F|5|6|7|31|8|@]|9|@]|A|$]]|$1|1G|3|-4|5|6|7|32|8|@]|9|@]|A|$]]]|1H|$1I|$5|1J|1K|1L|A|$1M|1N]]|1O|$5|1J|1K|1L|A|$1M|1N]]|1P|$5|1J|1K|1L|A|$1M|1Q]]|1R|$5|1J|1K|1L|A|$1M|1Q]]]]

<h1>To answer the question :</h1>
<ul>
<li>for VCS, it's <code>dev-master</code></li>
<li>for packagist, it's <code>*@stable</code></li>
</ul>
<hr>
<h1>For more about &quot;stabilizing&quot; or &quot;freezing&quot; composer versions</h1>
<h2>Freeze Make Stable</h2>
It's sometimes useful, especially during an audit, to grab latest versions of your requirements, that's why I made a composer package that make stable all your dependencies : <a href="https://github.com/MaximeCulea/Composer-Stable-Versions" rel="nofollow noreferrer">Composer Stable Versions</a> (<a href="https://github.com/MaximeCulea/Composer-Stable-Versions" rel="nofollow noreferrer">https://github.com/MaximeCulea/Composer-Stable-Versions</a>).
Using this command, your dependencies into composer.json will be automatically be changed from:
<code>&quot;wpackagist-plugin/wordpress-seo&quot;:&quot;6.2&quot;</code>
into:
<code>&quot;wpackagist-plugin/wordpress-seo&quot;:&quot;*@stable&quot;</code>
<h2>Freeze Composer Versions</h2>
If afterwards you plan doing the reverse thing to grab latest versions of your composer.lock which you tested your site against, especially useful while making a site live, have a look to an other of my composer command : <a href="https://github.com/MaximeCulea/Composer-Freeze-Versions" rel="nofollow noreferrer">Composer Freeze Versions</a> (<a href="https://github.com/MaximeCulea/Composer-Freeze-Versions" rel="nofollow noreferrer">https://github.com/MaximeCulea/Composer-Freeze-Versions</a>).
Using this command, your dependencies into composer.json will be automatically be locked:
<code>&quot;wpackagist-plugin/wordpress-seo&quot;:&quot;@stable&quot;</code>
into:
<code>&quot;wpackagist-plugin/wordpress-seo&quot;:&quot;6.2&quot;</code>
<hr>
Hope it helps.

blocks|key|3630321|text|如果你不是从github或类似的存储库获取包，而是从本地路径，"+path“类型，你必须在'composer.json‘文件中显式定义版本，它不会从本地git标签中找出它。此外，只有在packagist+github上不存在这样的软件包时，才会安装它，因此，如果它存在于本地路径名称“composer.json”字段中，则可能需要临时将其重命名为其他名称。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3630322|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you don't get your package from a github or a similar repository, but rather for example from the local path, &quot;path&quot; type, you have to have the version explicitly defined in the 'composer.json' file, it won't figure it out from the local git tags. Also, such a package will be installed only if it does not exist on the packagist, github and therefore it might be needed to be temporarily renamed if it exists in the local path composer.json &quot;name&quot; field, to something else.

I've recently come across the change in composer meaning that the default <code>minimum-stability</code> is <code>stable</code>, and rather than set this to <code>dev</code> I'd like to mark some of my libraries as stable.

I actually use two relevant branches, <code>release</code> and <code>dev</code> branched from <code>master</code>. Every so often something is merged into <code>release</code> and tagged as new version. 

How does composer determine the stability of my libraries, is there a naming convention for branches, version nums, a key in composer.json?

Thanks

How to mark code as stable using Composer?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我最近遇到了composer的变化，这意味着默认的minimum-stability是stable，而不是将其设置为dev，我想将我的一些库标记为稳定。我实际上使用了两个相关的分支，release和从master分支而来的dev。每隔一段时间，就会有一些东西被合并到release中并标记为新版本。composer如何确...

问如何使用Composer将代码标记为稳定？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用Composer将代码标记为稳定？EN