otel-upgrade

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

OpenTelemetry Upgrade

OpenTelemetry 升级

Find the highest stable target supported by the available repository evidence and provide concise, case-specific upgrade advice. Unless the user asks for implementation, assess the upgrade without changing project files.

根据现有仓库证据找到支持的最高稳定版本目标，并提供简洁、针对具体场景的升级建议。除非用户要求实施操作，否则评估升级时请勿修改项目文件。

Choose the workflow

选择工作流

Request or repository evidence	Read
Package manifests, lockfiles, APIs, SDKs, instrumentation libraries, exporters, plugins, or dependency constraints	Dependency upgrade
Collector binaries, images, charts, Operators, configuration, feature gates, components, OCB manifests, builds, or runtime behavior	Collector upgrade
A custom Collector involving independently versioned or third-party modules	Read the Collector workflow first, then the dependency workflow for relevant module constraints.

Read only the applicable reference. Read both when the upgrade crosses both surfaces.

请求或仓库证据	说明
包清单、锁定文件、API、SDK、工具库、导出器、插件或依赖约束	依赖升级
Collector二进制文件、镜像、图表、Operator、配置、功能开关、组件、OCB清单、构建或运行时行为	Collector升级
包含独立版本控制或第三方模块的自定义Collector	先阅读Collector工作流，再针对相关模块约束阅读依赖工作流。

仅阅读适用的参考文档。若升级同时涉及两类场景，则需阅读两份文档。

Shared instructions

通用说明

Inspect the repository and runtime evidence before choosing the workflow or assuming the ecosystem.
Establish the exact current and candidate versions. Record wrappers, distributions, artifacts, and embedded dependencies separately rather than treating one version as proof of another.
Query authoritative registries and primary upstream sources for current stable releases. Record the lookup date. Exclude prereleases unless requested; if no stable release meets a stated requirement, assess prereleases separately and label them clearly.
Distinguish the latest available stable release from the highest validated compatible candidate. Do not call a candidate validated when the relevant checks could not run.
Preserve the user's working tree by validating in a temporary copy, worktree, or equivalent isolated environment. Start with the latest stable candidate. If it fails, diagnose the cause and test selected lower versions when useful; do not assume compatibility is monotonic.
Connect upstream changes to this repository's actual usage and available downstream contracts. Treat unavailable consumers, environments, and exact-version coverage as unverified.
Use applicable specialized skills only when they are available. Otherwise use primary upstream sources and repository evidence, and report any resulting verification gaps.

Dependency resolution, compilation, configuration acceptance, and passing tests establish different and limited kinds of evidence. State exactly what each result demonstrates.

选择工作流或确定生态系统之前，先检查仓库与运行时证据。
确定当前版本与候选版本的精确信息。分别记录包装器、发行版、制品及嵌入式依赖，切勿将某个版本作为其他版本的证明依据。
查询权威注册表与上游主源获取当前稳定版本，并记录查询日期。除非用户要求，否则排除预发布版本；若没有稳定版本满足指定要求，则单独评估预发布版本并明确标注。
区分最新可用稳定版本与经验证的最高兼容候选版本。若相关检查无法运行，请勿称候选版本已通过验证。
通过在临时副本、工作树或等效隔离环境中验证，保留用户的工作树。从最新稳定候选版本开始验证。若验证失败，诊断原因并在必要时测试选定的较低版本；请勿假设兼容性是单调递增的。
将上游变更与本仓库的实际使用情况及可用的下游契约关联起来。将不可用的消费者、环境和精确版本覆盖范围视为未验证。
仅在相关专业技能可用时使用。否则使用上游主源与仓库证据，并报告由此产生的验证缺口。

依赖解析、编译、配置通过及测试合格代表不同且有限的证据类型。需明确说明每个结果能证明的内容。

Report

报告

Keep the report concise and tailored to the repository.

markdown

undefined

保持报告简洁且贴合仓库实际情况。

markdown

undefined

Recommendation

建议

Recommend upgrading

<subject>

from

<current>

<target>

, remaining on

<current>

, or deferring the upgrade. Explain the evidence, effort, and risk.

建议将

<subject>

从

<current>

升级至

<target>

、保持

<current>

版本不变，或推迟升级。说明相关证据、所需工作量及风险。

Relevant Findings

Proposed Upgrade Path

建议的升级路径

Give the smallest coordinated sequence of dependency, artifact, code, configuration, and rollout changes.

提供最小化的协调变更序列，包括依赖、制品、代码、配置及部署变更。

Validation

验证情况

State the exact candidates, artifacts, configurations, platforms, and checks covered, their results, and what those results demonstrate.

说明所覆盖的精确候选版本、制品、配置、平台及检查项，以及它们的结果和这些结果能证明的内容。

Remaining Risk

剩余风险

Mention only material behavior, environments, integrations, consumers, or artifacts that could not be verified. Omit this section when no material unverified areas were identified.


Link material upstream claims to authoritative release notes, documentation, or source. If the latest available version is not the highest validated compatible version, name both and explain the blocker.

仅提及无法验证的重大行为、环境、集成、消费者或制品。若未发现重大未验证领域，则省略此部分。


将上游的重要声明链接至官方发布说明、文档或源码。若最新可用版本并非经验证的最高兼容版本，请同时列出两者并说明阻碍因素。