编写软件版本兼容性说明
依据 CI、包元数据和现有政策整理版本与平台支持矩阵,指出承诺不一致处,并产出维护政策和版本检查说明。
完整提示词
<context>
You write the page readers check before installing or upgrading: which versions and platforms work. The page is a promise, so it must match reality. Projects routinely claim support for versions they never test, list runtimes that reached end of life, or forget to say what "supported" means. Experienced maintainers separate three levels: tested in CI on every change, supported (bugs will be fixed) and best effort or community. They tie support to the upstream lifecycle (for example dropping a runtime when it reaches end of life upstream, with notice), state which product versions still get fixes, and say how a version is dropped. Declared metadata (engines fields, minimum OS versions) must agree with the page, or package managers will tell readers something different.
<evidence>
{{evidence}}
</evidence>
{{#dimensions}}Dimensions to cover: {{dimensions}}{{/dimensions}}
</context>
<task>
1. Extract what is tested (from the CI matrix), what is declared (from package metadata), and what is promised (existing docs or policy). Show where they disagree.
2. Define the support levels used on the page in one line each.
3. Build the matrix for each dimension: version or platform, support level, and notes such as known issues or required flags. Only list something as tested if the CI evidence shows it.
4. Add a product versions table if the project has release lines: which versions get features, security fixes only, or nothing, with dates only if given.
5. Write the support policy: how new versions are added, how and with how much notice old ones are dropped, and how this relates to semantic versioning (dropping a runtime as a major or minor change, as the project decides).
6. Add a short "how to check your version" section with the relevant commands.
7. List the fixes needed so metadata, CI and the page agree, and decisions the maintainers must make.
</task>
<constraints>
- Never label a version as tested or supported without evidence; mark unclear ones as [decide].
- Do not invent end-of-life or release dates; tell the user to take upstream dates from the upstream project's own lifecycle page.
- Keep the matrix readable: one table per dimension, no more columns than needed.
{{> output/uncertainty}}
</constraints>
<output_format>
## Disagreements found
Table: item | tested | declared | promised.
## Support levels
Bullets.
## Compatibility
One table per dimension.
## Release lines
Table, or "Not applicable".
## Support policy
Short text.
## Check your version
Commands.
## Fixes and decisions
Bullets.
</output_format>可替换内容
- {{evidence}}
- {{#dimensions}}
- {{dimensions}}
- {{/dimensions}}
- {{> output/uncertainty}}
- [decide]
分类与标签
内容创作、技术文档、兼容性矩阵、版本支持政策