docs(release): v2.3.0 镜像落库补记（tag 腿已推 :2.3.0/:2.3/:latest，两戳定稿） - #164
Merged
Merged
Conversation
上一版 §2.1 只记到"main push 那条只发 :latest 与 :sha-，:2.3.0 尚未落库"。
标签腿已按 v2.2.5/v2.2.6 的先例补跑：gh workflow run docker-publish.yml --ref v2.3.0
→ run 36131581847，11:50:21Z 起、12:03:46Z 四个 manifest 推完（:2.3.0 / :2.3 / :latest /
:sha-cd80d735…，digest sha256:aa2494c4…），终态 12:21:57Z success 含 Trivy 腿。
证据只来自 run 日志的 pushing manifest for … 行：ghcr 包版本列表这个 token 读不到
（403 需 read:packages），这一点也写进记录，别让人以为做过外部复核。
于是 tag 创建 → 镜像落库 = 08:32:15Z → 12:03:46Z。中间 3.5 小时是"等人补标签腿"的空窗
而非构建耗时，已写明下次要在合并后立刻 dispatch。
自我修正一条：我原以为 tag 腿上 enable={{is_default_branch}} 会关掉 :latest，
日志证明它照样重推且与 :2.3.0 同一 digest。
Signed-off-by: ReSerendipity <ReSerendipity@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
接 #162 的第二笔，纯文档，1 file
docs/release-governance.md+12 −2。未自合并。补的是什么
#162 里 §2.1 停在"
:2.3.0尚未落库，待 dispatch"。标签腿已经补跑完，这里把结论与两戳定稿。实测（run
36131581847，workflow_dispatch --ref v2.3.0）2026-09-25T08:32:15Zv2.3.0与 Release（非 draft，4 资产齐）11:50:21Z12:03:46Z:2.3.0、:2.3、:latest、:sha-cd80d735…，digestsha256:aa2494c4…12:21:57ZResolve immutable scan ref+ Trivy 扫描腿）→ tag 创建 → 镜像落库 = 08:32:15Z → 12:03:46Z。并写明中间那 3.5 小时是"等人补标签腿"的空窗、不是构建耗时，下次要在合并后立刻 dispatch。
证据边界（照实记）
唯一来源是 run 日志的
pushing manifest for …行；ghcr 侧没有做外部复核 ——GET /users/reserendipity/packages/container/tts_multimodel/versions这个 token 回 403 需read:packages，包也非匿名可拉（与version.json里 v2.2.6 那段imagePullSecrets的记载一致）。不想让"三个标签都在"看起来比实际更有据。一条自我修正
我原先按
type=raw,value=latest,enable={{is_default_branch}}推断"tag 腿上不会重推:latest"，日志证明它照样推了:latest且与:2.3.0同一 digest —— 已把这条写进文档，免得下次有人按我的错推断去核。门禁
pytest tests/test_version_consistency.py→ 9 passed（未触碰任何版本位）；pre-commit 全 Passed；Signed-off-by齐。另：本 PR 只改
docs/**，所以在 #163 并入之前它仍会触发一次Docker Build（约 22 min）—— 那正好是 #163 那条paths-ignore的反面样本；#163 并了之后的纯文档 PR 就不该再出现这个作业。Refs: #145 #157 #159 #162 #163