Evan
598b641dd1
四处文档把「签名证书次数有限」当作设计理由，其中 docs/product-release.md 据此建议把若干修复攒成 一个版本以省额度。证书实际允许每月 3000 次签名，这个项目的发布频率远低于该量级，前提不成立。 改为如实说明，并把攒版本的真实理由（发布节奏与 release notes 的碎片化）写清楚——那个考量仍然 成立，只是和配额无关。
18 lines
823 B
JSON
18 lines
823 B
JSON
{
|
|
"$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json",
|
|
"packages": {
|
|
".": {
|
|
"release-type": "simple",
|
|
"package-name": "MetasequoiaImeWindows",
|
|
"include-component-in-tag": false,
|
|
"include-v-in-tag": true,
|
|
"version-file": "version.txt",
|
|
"draft": true,
|
|
"prerelease": true,
|
|
"force-tag-creation": true,
|
|
"pull-request-header": "This PR prepares the next Metasequoia IME for Windows release.",
|
|
"pull-request-footer": "The Release workflow merges this PR itself once CI is green on it, then builds, signs and publishes the release. Merging it by hand does the same thing, one run earlier. Every release spends one code signing signature; the certificate allows 3000 a month, so that is not a constraint."
|
|
}
|
|
}
|
|
}
|