Plan for cleaning up legacy images on docker.io/stellar/stellar-cli
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- docker
- 领域
- devops, documentation, release
调研方向
从 builds.json 和当前 pipeline 入手，确定哪些 Docker Hub 标签和摘要是正式生成的，然后盘点 docker.io/stellar/stellar-cli。查看 README，确定应在哪里记录发布策略。当 legacy-image 的处理方式、测试仓库和持续清理策略都已达成一致并记录下来时，即视为完成。
由索引模型根据 Issue 内容生成。
描述
What problem does your feature solve?
The docker.io/stellar/stellar-cli Docker Hub repository contains images that were published before this repo's pipeline existed. Those legacy images were not produced by the current builds.json-driven, digest-pinned pipeline, so they don't share its provenance, reproducibility, or pinning guarantees.
Leaving them in place creates a few problems:
- Users (and SEP-58 verifiers) can pull tags that look official but were not produced by the documented pipeline.
- The published tag/digest list no longer matches what
builds.jsonsays we publish, making the repo's source of truth misleading. - Ad-hoc/test pushes during pipeline development pollute the same namespace users consume from.
What would you like to see?
A plan with the following rough shape — exact details to be worked out in the issue/PR:
- Inventory every tag and digest currently on
docker.io/stellar/stellar-cliand classify each as:- produced by the current pipeline (matches an entry in
builds.json), or - legacy / not produced by the current pipeline.
- produced by the current pipeline (matches an entry in
- Remove (or otherwise retire — e.g. deprecate, hide, retag-and-archive) any images not produced by the current pipeline. Decide whether deletion is acceptable or whether we need a deprecation window first, given that downstream users and SEP-58
bldimgreferences may pin those digests. - Stop using
stellar/stellar-clias a test target. Pick a separate Docker Hub repo (e.g.stellar/stellar-cli-testor similar) for pipeline development and CI dry-runs, so the user-facing repo only ever receives pipeline-produced releases. - Document the policy in this repo's README so future maintainers don't re-pollute the production namespace.
- 主要语言
- Python
- 星标
- 0
- 派生
- 2
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
stellar/stellar-cli-docker 的其他 Issue
-
Unable to build versions to match deployed contracts可能已有人在做 @ethanfrey 于 127 天前认领。 未关闭bug
难度 4/5 3-5 天 新手友好度 45/100
stellar/stellar-cli-docker#23 · 2 条评论 ·
查看 stellar/stellar-cli-docker 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
WingedGuardian/GENesis-AGI#3375 ·
维护者通常 1 天内回复
-
curriculum documentation quality
难度 2/5 1-3 小时 新手友好度 75/100
githubnext/gh-aw-workshop#4601 ·
维护者通常 1 天内回复
-
approved Good First Issue scope: docs
难度 1/5 1 小时以内 新手友好度 85/100
hiero-ledger/hiero-sdk-python#2730 · 3 条评论 ·
维护者通常 1 天内回复