admin管理员组文章数量:1293237
The semantic-release documentation describes how to define the plugins
field within the semantic-release configuration (e.g. .releaserc
). Here's an example of a .releaserc file that I'm using in one of my projects:
{
"branches": ["main"],
"debug": true,
"plugins": [
"@semantic-release/commit-analyzer",
"@semantic-release/release-notes-generator",
"@semantic-release/changelog",
"@semantic-release/npm",
"@semantic-release/git",
"@semantic-release/github"
]
}
I've also seen a slightly different style of configuration that looks like this:
{
"branches": [
"main"
],
"verifyConditions": [
"@semantic-release/changelog",
"@semantic-release/npm",
"@semantic-release/git"
],
"prepare": [
"@semantic-release/changelog",
"@semantic-release/npm",
"@semantic-release/git"
],
"publish": [
[
"@semantic-release/npm",
{
"pkgRoot": "dist"
}
],
{
"path": "@semantic-release/github"
}
]
}
Here, instead of the plugins
field, there are fields named after some of the release steps (verifyConditions
, prepare
, and publish
).
I can't seem to find where this alternate style is documented. Where can I find docs about this?
Also, I'd like to understand what this means underneath the publish
field:
{
"path": "@semantic-release/github"
}
where is this documented?
Thanks in advance for any help!
本文标签: Question about semanticrelease configuration stylesStack Overflow
版权声明:本文标题:Question about semantic-release configuration styles - Stack Overflow 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1741572726a2386103.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论