Repository navigation
ci(release): 移除 floating latest + 删除 GPG workflow（§10.3/§10.6） - #190
Merged
Merged
Conversation
Signed-off-by: ReSerendipity <259081123+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.
§10.3 / §10.6 收敛：
docker-publish.yml移除type=raw,value=latest,enable={{is_default_branch}}（不再发布 floatinglatest）；.github/workflows/gpg-signed-release.yml；docs/release-governance.md同步现状：latest 差异清零、gpg 欠账清零，并把 provenance/sbom 未开的两条真实理由写明（①单架构 attestation 会多出 manifest；②发布链是 build(push:false) → 扫描 → 手动 push，attestation 仅在 buildx 自身 push 时附加）。备注：历史
:latesttag 仍留在 GHCR 上，但不再更新、不作下游引用基线。