Fix immutable-tag release recovery / 修正不可變標籤發行復原 - #8
Merged
Conversation
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.
繁體中文
修改內容
main上已修復的自動化腳本。根因與影響
手動復原流程雖已正確鎖定發行標籤，最後工作卻連同發布腳本一起切回舊提交，使已合併的修正無法生效。本修正不移動標籤、不改變套件來源，也不放寬任何安全閘門。
驗證
简体中文
恢复既有不可变 RC 标签时，四平台安装包仍由标签固定提交构建，只有最终发布协调步骤使用
main中已修复的脚本。此修正不移动标签、不改变安装包来源，也不放宽安全门槛；Packaging Audit 已全部通过。English
During recovery of an existing immutable RC tag, all four platform packages remain built from the tagged commit. Only the final release-orchestration step uses the repaired workflow from
main. The change neither moves the tag nor weakens release gates. The Packaging Audit passes in full.日本語
既存の不変 RC タグを復旧する際も、4 プラットフォームのパッケージはタグで固定されたコミットからビルドします。最終的なリリース制御だけが
mainの修正版を使用します。タグの移動、成果物の出所変更、安全ゲートの緩和はありません。Packaging Audit はすべて合格しました。