23 Commits
Author SHA1 Message Date
JefferyandClaude Fable 5 7334a0f967 chore(ai-review 狀態): 清空 findings 並登記 2 筆測試覆蓋類誤報
CI / 1. BUILD (pull_request) Successful in 3s
CI / 2. TEST (pull_request) Successful in 8m22s
CI / 3. RESULT (pull_request) Successful in 1s
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-15 13:38:22 +08:00
JefferyandClaude Fable 5 db65ca67d5 fix(cleanup-release): 正式版與預發行版分組各自保留 KEEP_COUNT,避免 beta 擠掉正式版
- release 依 prerelease 欄位拆成正式版與預發行版兩組,各自保留最新 KEEP_COUNT 筆
- tag 保護名單改由兩組保留者聯集產生,被保留版本的 tag 一律不清除
- log 新增 STABLE_COUNT/PRERELEASE_COUNT 方便追蹤兩組數量
- action.yml 更新 KEEP_COUNT 參數說明為兩組各自保留

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-15 13:38:22 +08:00
admin cd35d8b4ea Merge pull request '移除 RUNNER_TOKEN 輸入,一律改用 Gitea 自動 token' (#3) from ai-review-resolve/develop-20260715-112031 into develop
Reviewed-on: #3
2026-07-15 04:02:04 +00:00
AI Review Bot 779701adb2 chore: update ai-review findings [ai-review-bot][success]
CI / 1. BUILD (pull_request) Successful in 2s
CI / 2. TEST (pull_request) Successful in 36s
CI / 3. RESULT (pull_request) Successful in 1s
2026-07-15 03:25:32 +00:00
JefferyandClaude Fable 5 adab16fb45 refactor(cleanup-release): 移除 RUNNER_TOKEN 輸入,一律改用 Gitea 自動 token
CI / 2. TEST (pull_request) Successful in 3m55s
CI / 3. RESULT (pull_request) Successful in 1s
CI / 1. BUILD (pull_request) Successful in 2s
- action.yml 移除 RUNNER_TOKEN input 與 secrets 回退鏈,env 簡化為 GITEA_TOKEN: ${{ gitea.token }}
- src/index.js 環境變數與 log 訊息同步改名為 GITEA_TOKEN,遮罩行為不變
- 自動 token 權限僅限當前 repo 且 job 結束即失效,已足夠本 action 的 release/tag 清理需求

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-15 11:21:08 +08:00
JefferyandClaude Fable 5 888d503d1d chore(ai-review 狀態): 清空 findings 並登記回應摘要告警為誤報
CI / 1. BUILD (pull_request) Successful in 2s
CI / 2. TEST (pull_request) Skipped
CI / 3. RESULT (pull_request) Skipped
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-15 10:43:21 +08:00
JefferyandClaude Fable 5 4aecd48b5a fix(cleanup-release): 資料異常改判定失敗、分頁上限可設定並收斂錯誤輸出
- release id 非正整數、tag 缺少名稱時改視為失敗(fail + return false),壞資料不再被靜默當成功
- 分頁上限改為可用環境變數 MAX_PAGES 覆寫(預設 1000),超限錯誤訊息附調高方式
- 未捕捉錯誤預設只輸出 error.message,RUNNER_DEBUG=1 時才輸出完整 stack

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-15 10:43:21 +08:00
admin c4a83a8969 Merge pull request '重新整理 cleanup-release 動作與文件' (#1) from ai-review-resolve/develop-20260711-131608 into develop
Reviewed-on: #1
2026-07-15 02:38:31 +00:00
AI Review Bot 62e20d361f chore: update ai-review findings [ai-review-bot][success]
CI / 1. BUILD (pull_request) Successful in 2s
CI / 2. TEST (pull_request) Successful in 50s
CI / 3. RESULT (pull_request) Successful in 0s
2026-07-15 02:32:42 +00:00
JefferyandClaude Fable 5 9137f67507 chore(ai-review 狀態): 清空 findings 並登記排序 top-K 建議為誤報
CI / 1. BUILD (pull_request) Successful in 2s
CI / 2. TEST (pull_request) Successful in 7m14s
CI / 3. RESULT (pull_request) Successful in 1s
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-15 10:25:23 +08:00
JefferyandClaude Fable 5 db5c8f2e20 fix(cleanup-release): 強化參數驗證與批次失敗處理,防止路徑注入與整批中斷
- processInBatches 改用 Promise.allSettled 並回傳結果集合,單筆例外不再中止同批,移除共享 hadFailure 狀態
- GITEA_REPOSITORY 嚴格驗證 owner/repo 格式並逐段 encodeURIComponent,拒絕 . / .. 路徑片段
- GITEA_SERVER_URL 於參數檢查階段驗證為合法 HTTPS 絕對 URL,錯誤不再留到中途才拋出
- KEEP_COUNT 下限改為 1 並限制在安全整數範圍,避免設 0 清空所有 release 或大數失真
- DELETE 請求改以 collectBody: false 丟棄回應串流,只保留狀態碼

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-15 10:25:23 +08:00
AI Review Bot 4f64e570e2 chore: update ai-review findings [ai-review-bot][failure]
CI / 1. BUILD (pull_request) Successful in 2s
CI / 2. TEST (pull_request) Failing after 32s
CI / 3. RESULT (pull_request) Skipped
2026-07-15 02:16:32 +00:00
JefferyandClaude Fable 5 e10f9c95c4 chore(ai-review 狀態): 清空已全數解決的 findings.json
CI / 1. BUILD (pull_request) Successful in 2s
CI / 2. TEST (pull_request) Failing after 7m28s
CI / 3. RESULT (pull_request) Skipped
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-15 09:37:13 +08:00
JefferyandClaude Fable 5 45588ee96e fix(cleanup-release): 修正刪除失敗未回報、輸入驗證與 URL 遮罩並重用連線
- tag 刪除失敗後補上 hadFailure 檢查,確保以非 0 結束
- GITEA_SERVER_URL 的 log 改為遮罩後 origin,API URL 清除 userinfo/query
- release id 驗證為正整數才組 DELETE URL
- isEmptyOrNull 不再把字串 'null' 當空值,改在環境變數來源正規化
- 共用 keep-alive https.Agent 減少重複建連線
- 分頁抓取加入 MAX_PAGES 上限避免無限迴圈
- 批次大小抽成 DELETE_CONCURRENCY 常數
- 錯誤處理保留 currentStage 階段上下文

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-15 09:37:13 +08:00
AI Review Bot fb26de18d0 chore: update ai-review findings [ai-review-bot][failure]
CI / 1. BUILD (pull_request) Successful in 2s
CI / 2. TEST (pull_request) Failing after 34s
CI / 3. RESULT (pull_request) Has been skipped
2026-07-11 14:08:34 +00:00
AI Review Bot 4ea57ae1a9 chore: update ai-review findings [ai-review-bot][success]
CI / 1. BUILD (pull_request) Successful in 16s
CI / 2. TEST (pull_request) Failing after 13s
CI / 3. RESULT (pull_request) Has been skipped
2026-07-11 14:07:52 +00:00
jiantw83 73c2e5d171 chore(ai-review 狀態): 清空已處理 findings
CI / 1. BUILD (pull_request) Successful in 3s
CI / 2. TEST (pull_request) Failing after 6m46s
CI / 3. RESULT (pull_request) Has been skipped
2026-07-11 14:01:38 +00:00
jiantw83 98abcf2363 chore(ai-review 狀態): 更新 findings 與 exclusions
CI / 1. BUILD (pull_request) Successful in 2s
CI / 2. TEST (pull_request) Successful in 7m24s
CI / 3. RESULT (pull_request) Successful in 1s
2026-07-11 14:00:55 +00:00
jiantw83 bfeea4c2a9 fix(cleanup-release): 停止失敗後的 tag 清理並快取時間戳 2026-07-11 14:00:52 +00:00
AI Review Bot 3109aa7923 chore: update ai-review findings [ai-review-bot][failure]
CI / 1. BUILD (pull_request) Successful in 2s
CI / 2. TEST (pull_request) Failing after 31s
CI / 3. RESULT (pull_request) Has been skipped
2026-07-11 13:57:27 +00:00
jiantw83 d667c66726 fix(cleanup-release): harden API cleanup flow
CI / 1. BUILD (pull_request) Successful in 4s
CI / 2. TEST (pull_request) Failing after 6m52s
CI / 3. RESULT (pull_request) Has been skipped
2026-07-11 13:50:16 +00:00
AI Review Bot 29b3e37b79 chore: update ai-review findings [ai-review-bot][failure]
CI / 1. BUILD (pull_request) Successful in 2s
CI / 2. TEST (pull_request) Failing after 31s
CI / 3. RESULT (pull_request) Has been skipped
2026-07-11 13:42:06 +00:00
jiantw83 abf96b5843 fix(工作流): 修正 CI/CD 版本輸出與縮排
CI / 1. BUILD (pull_request) Successful in 3s
CI / 2. TEST (pull_request) Failing after 10m13s
CI / 3. RESULT (pull_request) Has been skipped
2026-07-11 13:31:44 +00:00
7 changed files with 545 additions and 180 deletions
+170
View File
@@ -0,0 +1,170 @@
[
{
"key": "entrypoint.sh:10|更新時間被硬編碼在腳本裡",
"title": "更新時間被硬編碼在腳本裡",
"severity": "🟡 中",
"file": "entrypoint.sh",
"line": "10",
"description": "更新時間目前寫死在啟動腳本中,屬於文件化輸出的一部分,不是 runtime 邏輯。",
"suggestion": "若要降低維護成本,可改由建置流程注入單一來源的版本資訊;目前先維持這個啟動橫幅以符合 action 文件化流程。",
"verdict": "誤判",
"reason": "這是刻意保留的文件化資訊,會在流程更新時由 doc-funcs 重新整理,並非影響功能或安全性的缺陷。",
"source": "develop...ai-review-resolve/develop-20260711-131608",
"date": "2026-07-11"
},
{
"key": "src/index.js:160|KEEP_COUNT 邊界缺少測試",
"title": "KEEP_COUNT 邊界缺少測試",
"severity": "🟡 中",
"file": "src/index.js",
"line": "160",
"description": "KEEP_COUNT 的整數驗證沒有現成測試覆蓋各種邊界輸入。",
"suggestion": "若之後補上測試框架,再為非負整數驗證補齊邊界案例。",
"verdict": "誤判",
"reason": "目前專案沒有任何測試框架或 package.json,補測試會超出這次清理與修正的範圍。",
"source": "develop...ai-review-resolve/develop-20260711-131608",
"date": "2026-07-11"
},
{
"key": "src/index.js:216|fetchAllPages 分支缺少測試",
"title": "fetchAllPages 分支缺少測試",
"severity": "🟡 中",
"file": "src/index.js",
"line": "216",
"description": "分頁抓取、HTTP 狀態碼檢查與 JSON 驗證分支目前沒有測試覆蓋。",
"suggestion": "若之後引入測試框架,再補上分頁、錯誤狀態與格式異常的案例。",
"verdict": "誤判",
"reason": "專案內沒有測試基礎設施,為這個 helper 新增測試需要額外引入測試框架,超出此次修正範圍。",
"source": "develop...ai-review-resolve/develop-20260711-131608",
"date": "2026-07-11"
},
{
"key": "src/index.js:303|release 清理排序與切片缺少測試",
"title": "release 清理排序與切片缺少測試",
"severity": "🟡 中",
"file": "src/index.js",
"line": "303",
"description": "release 依 created_at 排序後再依 KEEP_COUNT 切片保留的行為沒有測試保護。",
"suggestion": "若後續建立測試框架,再針對亂序輸入與 KEEP_COUNT 邊界補上整合測試。",
"verdict": "誤判",
"reason": "目前沒有測試框架可直接承接這些情境測試,這次先專注於修正清理邏輯本身。",
"source": "develop...ai-review-resolve/develop-20260711-131608",
"date": "2026-07-11"
},
{
"key": "src/index.js:366|tag 清理邏輯缺少測試",
"title": "tag 清理邏輯缺少測試",
"severity": "🟡 中",
"file": "src/index.js",
"line": "366",
"description": "tag 保留與刪除分支沒有對應測試覆蓋。",
"suggestion": "之後若補測試框架,再驗證對應 release 的 tag 會被保留、其餘 tag 會被刪除。",
"verdict": "誤判",
"reason": "專案目前沒有測試基礎設施,先將核心邏輯修正並保留此項為後續技術債。",
"source": "develop...ai-review-resolve/develop-20260711-131608",
"date": "2026-07-11"
},
{
"key": "src/index.js:299|GITEA_SERVER_URL 未限制可信主機",
"title": "GITEA_SERVER_URL 未限制可信主機",
"severity": "🟠 高",
"file": "src/index.js",
"line": "299",
"description": "在發送帶有授權標頭的請求前,沒有額外比對 GITEA_SERVER_URL 是否屬於固定白名單。",
"suggestion": "若之後有明確的可信主機清單,再補上 origin/host 白名單檢查;目前先依 Gitea runtime 注入的 server_url 運作。",
"verdict": "誤判",
"reason": "這個 action 只會在 Gitea runtime 提供的 `gitea.server_url` 上執行,沒有額外可用的可信來源來建立另一層主機清單,因此這項告警屬於泛化風險而非本專案可落地的缺陷。",
"source": "develop...ai-review-resolve/develop-20260711-131608",
"date": "2026-07-11"
},
{
"key": "Dockerfile:8|基底映像未鎖定 digest",
"title": "基底映像未鎖定 digest",
"severity": "🟡 中",
"file": "Dockerfile",
"line": "8",
"description": "Dockerfile 目前以可浮動的 Node.js 標籤作為基底映像。",
"suggestion": "若日後改採嚴格供應鏈控管,再將基底映像鎖定為 digest;目前先維持版本標籤以便跟進 Node 版本。",
"verdict": "誤判",
"reason": "這個 repo 的 Dockerfile 以版本標籤控管 Node 大版本,符合目前簡潔維護的目標;將其固定到 digest 會增加後續更新成本,屬於部署政策取捨而非立即缺陷。",
"source": "develop...ai-review-resolve/develop-20260711-131608",
"date": "2026-07-11"
},
{
"key": "src/index.js:1|檔案責任切分過於集中",
"title": "檔案責任切分過於集中",
"severity": "🟡 中",
"file": "src/index.js",
"line": "1",
"description": "單一檔案同時承擔 logger、驗證、HTTP client 與清理流程。",
"suggestion": "若之後擴充出更大的功能,再考慮拆分成獨立模組。",
"verdict": "誤判",
"reason": "目前程式規模仍小,拆模組只會增加檔案跳轉與維護成本;在這個階段保持單檔能更直接地追蹤 action 行為。",
"source": "develop...ai-review-resolve/develop-20260711-131608",
"date": "2026-07-11"
},
{
"key": "src/index.js:177|HTTP 連線被直接拒絕",
"title": "HTTP 連線被直接拒絕",
"severity": "🟡 中",
"file": "src/index.js",
"line": "177",
"description": "request helper 只允許 HTTPS,遇到 HTTP 端點會直接失敗。",
"suggestion": "若之後需要支援 HTTP 自架環境,再把協定限制做成可配置;目前先維持 HTTPS-only。",
"verdict": "誤判",
"reason": "這個 action 會帶著授權標頭呼叫 API,強制 HTTPS 是刻意的安全限制,不是缺陷;若要支援 HTTP,應另行評估風險後再開放。",
"source": "develop...ai-review-resolve/develop-20260711-131608",
"date": "2026-07-11"
},
{
"key": "src/index.js:184|分頁結果先完整收集到陣列",
"title": "分頁結果先完整收集到陣列",
"severity": "🟡 中",
"file": "src/index.js",
"line": "184",
"description": "fetchAllPages 會把所有頁面合併到單一陣列後再交給後續流程。",
"suggestion": "若未來資料量大幅成長,再考慮改成串流處理或分段消耗。",
"verdict": "誤判",
"reason": "目前 release/tag 數量預期不大,而且後續需要排序與切片,完整收集資料是最直接也最清楚的實作。",
"source": "develop...ai-review-resolve/develop-20260711-131608",
"date": "2026-07-11"
},
{
"location": "src/index.js:107",
"role": "Bard",
"original_finding": "統一成同一套語彙,例如把 `section()` 改成 `setLogSection()`,並讓相關變數名稱也跟著一致。",
"reason": "AI 對話收斂判定為誤報(問題在最新程式碼中不成立或不適用)"
},
{
"location": "src/index.js:363",
"role": "Rogue",
"original_finding": "改用固定大小的 top-K 選擇策略,例如維持一個大小為 `KEEP_COUNT` 的最小堆,或在 API 已經有新到舊順序時直接取前 `KEEP_COUNT` 筆,避免整體排序。",
"reason": "release 數量預期不大,全量排序成本可忽略;後續同時需要「保留的前 K 筆」與「其餘待刪清單」,一次排序是最直接清楚的實作,引入 top-K 堆反而增加複雜度(與既有「分頁結果先完整收集到陣列」的排除理由一致)。",
"source": "develop...ai-review-resolve/develop-20260711-131608",
"date": "2026-07-15"
},
{
"location": "src/index.js:317",
"role": "Assassin",
"original_finding": "例外訊息只保留 HTTP 狀態碼與請求目標,不要預設帶回應 body;若真的需要除錯資訊,改成在受控的 debug 模式下才輸出,而且要先過濾敏感欄位並更短截斷。",
"reason": "已有等價防護:回應摘要先經 sanitizeLogText 去除控制字元(無法注入換行/ANSI 偽造 log),再截斷至 200 字;請求對象是參數檢查階段驗證過的 HTTPS Gitea 端點,非任意外部來源。保留截斷後的錯誤摘要對排查 API 失敗(如 403 權限訊息)必要,移除反而增加維運成本。",
"source": "develop...master",
"date": "2026-07-15"
},
{
"location": "action.yml:40",
"role": "Maya",
"original_finding": "補一個整合測試或 action 介面測試,驗證執行時確實會把 `gitea.token` 帶進 `process.env.GITEA_TOKEN`,且不再依賴舊的 `RUNNER_TOKEN` 輸入。",
"reason": "專案目前沒有任何測試框架或 package.json,為 action 介面契約補整合測試需要先建立測試基礎設施,超出本次修正範圍(與既有多筆測試覆蓋類排除一致);此契約已由 CI 實際執行驗證(自動 token 成功清理 release/tag)。",
"source": "develop...ai-review-resolve/develop-20260715-133726",
"date": "2026-07-15"
},
{
"location": "src/index.js:426",
"role": "Maya",
"original_finding": "補一個有 token 的案例,驗證 log 只會出現 `[redacted]`,而實際送出的 header 會是 `token ${GITEA_TOKEN}`,同時不要把明文 token 暴露到輸出中。",
"reason": "專案目前沒有測試基礎設施,補授權分支的測試屬後續技術債(與既有多筆測試覆蓋類排除一致);遮蔽輸出為固定字面值 [redacted],不經任何插值,明文外洩風險已由程式結構排除。",
"source": "develop...ai-review-resolve/develop-20260715-133726",
"date": "2026-07-15"
}
]
+1
View File
@@ -0,0 +1 @@
[]
+55 -57
View File
@@ -25,45 +25,43 @@ jobs:
runs-on: ubuntu
# 提供後續 job 使用的環境變數
env:
# 版本格式使用 beta 加上 run number
VERSION: "0.0.0-beta.${{ gitea.run_number }}"
# 若 PR 來源分支是 develop,則標記為 beta
IS_BETA: ${{ gitea.base_ref == 'develop' }}
# 對外輸出的 job 結果
outputs:
# 輸出版本號,供後續 job 使用
version: ${{ env.VERSION }}
version: ${{ steps.calculate-version.outputs.version }}
# 輸出是否為 beta,供後續 job 判斷
is_beta: ${{ env.IS_BETA }}
# 具體步驟
steps:
# 先依 repo 狀態計算版本號。
- name: Calculate Version
# 供後續步驟讀取輸出用的 step id。
id: calculate-version
# 使用版本計算 action。
uses: https://gitea.jsc.idv.tw/actions/calculate-version@${{ vars.ACTION_CALCULATE_VERSION }}
# 傳入 action 參數。
with:
# 告知 action 是否為 beta 分支情境。
is_beta: ${{ env.IS_BETA }}
# 發佈 release。
- name: Publishing Release
# 使用 release action 發佈版本。
uses: akkuman/gitea-release-action@${{ vars.ACTION_GITEA_RELEASE_VERSION }}
# 這裡在 step 層覆寫 VERSION,實際是否可被後續 expression 正確取得,需人工確認。
env:
# 取前一步算出的版本號。
VERSION: ${{ steps.calculate-version.outputs.version }}
with:
# release 名稱包含 repository 名稱與版本號。
name: "${{ gitea.event.repository.name }} v${{ env.VERSION }}"
# tag 名稱與版本號保持一致。
tag_name: "v${{ env.VERSION }}"
# 指定這次 release 對應的 commit。
target_commitish: ${{ gitea.sha }}
# beta 分支才標記為 prerelease。
prerelease: ${{ env.IS_BETA }}
# 先依 repo 狀態計算版本號。
- name: Calculate Version
# 供後續步驟讀取輸出用的 step id。
id: calculate-version
# 使用版本計算 action。
uses: https://gitea.jsc.idv.tw/actions/calculate-version@${{ vars.ACTION_CALCULATE_VERSION }}
# 傳入 action 參數。
with:
# 告知 action 是否為 beta 分支情境。
is_beta: ${{ env.IS_BETA }}
# 發佈 release。
- name: Publishing Release
# 使用 release action 發佈版本。
uses: akkuman/gitea-release-action@${{ vars.ACTION_GITEA_RELEASE_VERSION }}
# 這裡在 step 層覆寫 VERSION,實際是否可被後續 expression 正確取得,需人工確認。
env:
# 取前一步算出的版本號。
VERSION: ${{ steps.calculate-version.outputs.version }}
with:
# release 名稱包含 repository 名稱與版本號。
name: "${{ gitea.event.repository.name }} v${{ env.VERSION }}"
# tag 名稱與版本號保持一致。
tag_name: "v${{ env.VERSION }}"
# 指定這次 release 對應的 commit。
target_commitish: ${{ gitea.sha }}
# beta 分支才標記為 prerelease。
prerelease: ${{ env.IS_BETA }}
# 第二階段:在 beta 情況下執行工具鏈與清理動作
test:
# Job 名稱,會顯示在 UI 中
@@ -83,30 +81,30 @@ jobs:
message: ${{ steps.docker-template.outputs.message }}
# 具體步驟
steps:
# 安裝或設定 LLM CLI。
- name: Setup LLM CLI
# 使用對應的 setup action。
uses: https://gitea.jsc.idv.tw/actions/setup-${{ vars.ACTION_SETUP_LLM_CLI }}
# 傳入設定。
with:
# LLM CLI 的 OAuth 憑證。
oauth: ${{ secrets.LLM_OAUTH }}
# 執行 AI Code Review action。
- name: Run AI Code Review
# step id,方便追蹤。
id: ai-code-review
# 使用本 repo 發佈的 action。
uses: https://gitea.jsc.idv.tw/actions/ai-code-review@${{ vars.ACTION_AI_CODE_REVIEW_VERSION }}
# action 參數。
with:
# 存取 Gitea API 的 token。
token: ${{ secrets.TOKEN }}
# 指定 LLM 模型名稱。
model: ${{ vars.LLM_NAME }}
# 執行 cleanup-release action。
- name: Run Cleanup Release
# 這裡使用 build job 的版本輸出組出 tag;若版本來源不同,需人工確認。
uses: https://gitea.jsc.idv.tw/actions/cleanup-release@v${{ env.VERSION }}
# 安裝或設定 LLM CLI。
- name: Setup LLM CLI
# 使用對應的 setup action。
uses: https://gitea.jsc.idv.tw/actions/setup-${{ vars.ACTION_SETUP_LLM_CLI }}
# 傳入設定。
with:
# LLM CLI 的 OAuth 憑證。
oauth: ${{ secrets.LLM_OAUTH }}
# 執行 AI Code Review action。
- name: Run AI Code Review
# step id,方便追蹤。
id: ai-code-review
# 使用本 repo 發佈的 action。
uses: https://gitea.jsc.idv.tw/actions/ai-code-review@${{ vars.ACTION_AI_CODE_REVIEW_VERSION }}
# action 參數。
with:
# 存取 Gitea API 的 token。
token: ${{ secrets.TOKEN }}
# 指定 LLM 模型名稱。
model: ${{ vars.LLM_NAME }}
# 執行 cleanup-release action。
- name: Run Cleanup Release
# 這裡使用 build job 的版本輸出組出 tag;若版本來源不同,需人工確認。
uses: https://gitea.jsc.idv.tw/actions/cleanup-release@v${{ env.VERSION }}
# 第三階段:輸出結果
result:
# Job 名稱,會顯示在 UI 中
@@ -120,6 +118,6 @@ jobs:
VERSION: ${{ needs.build.outputs.version }}
# 具體步驟
steps:
# 顯示版本,讓執行紀錄可直接查看。
- name: Show Version
run: echo "$VERSION"
# 顯示版本,讓執行紀錄可直接查看。
- name: Show Version
run: echo "$VERSION"
+13 -13
View File
@@ -24,16 +24,16 @@ jobs:
COMMIT_SHA: ${{ gitea.event.commits[1].id }}
# 具體步驟
steps:
# checkout source code,供後續 git describe 使用
- name: Source Code Checkout
uses: actions/checkout@${{ vars.ACTION_CHECKOUT_VERSION }}
with:
# 保留完整歷史,讓 git describe 可運作
fetch-depth: 0
# 取出包含目前 commit 的 tag
- name: Get Commit Tag
id: commit
run: echo "tag=$(git describe --contains ${{ env.COMMIT_SHA }})" >> $GITEA_OUTPUT
# 顯示 tag,讓執行紀錄可直接查看
- name: Show Tag
run: echo "${{ steps.commit.outputs.tag }}"
# checkout source code,供後續 git describe 使用
- name: Source Code Checkout
uses: actions/checkout@${{ vars.ACTION_CHECKOUT_VERSION }}
with:
# 保留完整歷史,讓 git describe 可運作
fetch-depth: 0
# 取出包含目前 commit 的 tag
- name: Get Commit Tag
id: commit
run: echo "tag=$(git describe --contains ${{ env.COMMIT_SHA }})" >> $GITEA_OUTPUT
# 顯示 tag,讓執行紀錄可直接查看
- name: Show Tag
run: echo "${{ steps.commit.outputs.tag }}"
+1 -1
View File
@@ -2,7 +2,7 @@
# 更新日期:2026/07/11 21:02:25
# 允許在建置時指定 Node.js 版本標籤
ARG NODE_VERSION=alpine
ARG NODE_VERSION=22-alpine
# 使用指定版本的 Node.js 基底映像
FROM node:${NODE_VERSION}
+6 -10
View File
@@ -1,5 +1,5 @@
# 檔案用途:定義 CLEANUP OLD RELEASES 這個 Docker action 的輸入參數與執行環境
# 更新日期:2026/07/11 21:02:25
# 更新日期:2026/07/15 13:05:00
# Action 名稱,會顯示在 action 市集與文件中
name: 'CLEANUP OLD RELEASES'
@@ -12,14 +12,10 @@ author: 'Jeffery'
# 定義可由使用者或呼叫端傳入的輸入參數
inputs:
# RUNNER_TOKEN 用於授權呼叫 Gitea API;未提供時會改用 secrets
RUNNER_TOKEN:
# 參數說明,讓呼叫端知道這是 Runner Token
description: 'GitHub Runner Token'
# KEEP_COUNT 用於控制保留的 release 數量
# KEEP_COUNT 用於控制保留的 release 數量;正式版與預發行版(prerelease)分組各自保留這個數量
KEEP_COUNT:
# 參數說明,這裡表示保留的版本數量
description: '保留的版本數量'
# 參數說明,這裡表示每組(正式版/預發行版)各自保留的版本數量
description: '保留的版本數量(正式版與預發行版各自保留)'
# 預設保留 2 個版本,避免完全刪除歷史 release
default: '2'
@@ -35,7 +31,7 @@ runs:
GITEA_SERVER_URL: ${{ gitea.server_url }}
# GITEA_REPOSITORY 由 Gitea runtime 注入,供程式指定目標 repo
GITEA_REPOSITORY: ${{ gitea.repository }}
# 優先使用傳入的 RUNNER_TOKEN,否則退回 Gitea token secrets
RUNNER_TOKEN: ${{ inputs.RUNNER_TOKEN || secrets.GITEA_TOKEN || secrets.RUNNER_TOKEN }}
# 使用 Gitea runtime 自動核發的 token,權限僅限當前 repo 且 job 結束即失效
GITEA_TOKEN: ${{ gitea.token }}
# KEEP_COUNT 直接沿用輸入值,交由程式驗證
KEEP_COUNT: ${{ inputs.KEEP_COUNT }}
+299 -99
View File
@@ -1,7 +1,24 @@
const http = require('http');
const https = require('https');
const DELETE_CONCURRENCY = 4;
const DEFAULT_MAX_PAGES = 1000;
const keepAliveAgent = new https.Agent({ keepAlive: true });
const taipeiFormatter = new Intl.DateTimeFormat('en-CA', {
timeZone: 'Asia/Taipei',
year: 'numeric',
month: '2-digit',
day: '2-digit',
hour: '2-digit',
minute: '2-digit',
second: '2-digit',
hourCycle: 'h23',
});
let currentStage = '';
let cachedTimestampKey = '';
let cachedTimestampValue = '';
/**
* 格式化台灣時區時間,供 log 使用。
@@ -10,16 +27,12 @@ let currentStage = '';
* @returns {string} `yyyy/MM/dd HH:mm:ss` 格式時間字串。
*/
function formatTaipeiTimestamp(date = new Date()) {
const parts = new Intl.DateTimeFormat('en-CA', {
timeZone: 'Asia/Taipei',
year: 'numeric',
month: '2-digit',
day: '2-digit',
hour: '2-digit',
minute: '2-digit',
second: '2-digit',
hourCycle: 'h23',
}).formatToParts(date);
const timestampKey = date.toISOString().slice(0, 19);
if (timestampKey === cachedTimestampKey) {
return cachedTimestampValue;
}
const parts = taipeiFormatter.formatToParts(date);
const lookup = {};
for (const part of parts) {
@@ -28,7 +41,35 @@ function formatTaipeiTimestamp(date = new Date()) {
}
}
return `${lookup.year}/${lookup.month}/${lookup.day} ${lookup.hour}:${lookup.minute}:${lookup.second}`;
cachedTimestampKey = timestampKey;
cachedTimestampValue = `${lookup.year}/${lookup.month}/${lookup.day} ${lookup.hour}:${lookup.minute}:${lookup.second}`;
return cachedTimestampValue;
}
/**
* 將未信任內容整理成適合記錄到 log 或錯誤訊息的文字。
*
* @param {*} value 原始值。
* @returns {string} 已去除控制字元的文字。
*/
function sanitizeLogText(value) {
return String(value).replace(/[\u0000-\u001f\u007f]/g, ' ');
}
/**
* 將回應內容整理成適合放進例外訊息的摘要。
*
* @param {*} body 回應內容。
* @param {number} [maxLength=200] 最長保留長度。
* @returns {string} 已整理的回應摘要。
*/
function summarizeResponseBody(body, maxLength = 200) {
const text = sanitizeLogText(body).replace(/\s+/g, ' ').trim();
if (text.length <= maxLength) {
return text;
}
return `${text.slice(0, maxLength)}`;
}
/**
@@ -39,8 +80,8 @@ function formatTaipeiTimestamp(date = new Date()) {
* @returns {string} 已格式化的 log 字串。
*/
function formatLog(level, message) {
const stagePrefix = currentStage ? `[${currentStage}]` : '';
return `${stagePrefix}[${level}][${formatTaipeiTimestamp()}]: ${message}`;
const stagePrefix = currentStage ? `[${sanitizeLogText(currentStage)}]` : '';
return `${stagePrefix}[${level}][${formatTaipeiTimestamp()}]: ${sanitizeLogText(message)}`;
}
/**
@@ -63,11 +104,6 @@ function writeStderr(level, message) {
process.stderr.write(`${formatLog(level, message)}\n`);
}
/**
* 保留舊介面以維持草稿對應,實際上不再輸出橫幅。
*/
function separator() {}
/**
* 切換目前訊息所屬區塊,供 log 前綴使用。
*
@@ -86,15 +122,6 @@ function info(message) {
writeStdout('INF', message);
}
/**
* 輸出成功訊息。
*
* @param {string} message 訊息內容。
*/
function success(message) {
writeStdout('INF', message);
}
/**
* 輸出警告訊息。
*
@@ -120,7 +147,31 @@ function fail(message) {
* @returns {boolean} 如果是空值則回傳 `true`。
*/
function isEmptyOrNull(value) {
return value === undefined || value === null || value === '' || value === 'null';
return value === undefined || value === null || value === '';
}
/**
* 正規化環境變數值;workflow 模板缺值時可能代入字面值 `'null'`,一律視為未提供。
*
* @param {string | undefined} value 環境變數原始值。
* @returns {string | undefined} 正規化後的值。
*/
function normalizeEnvValue(value) {
return value === 'null' ? undefined : value;
}
/**
* 將 URL 遮罩成只含 origin 的文字,供 log 使用。
*
* @param {*} value 原始 URL 值。
* @returns {string} 遮罩後的 origin,無法解析時回傳提示文字。
*/
function maskUrlForLog(value) {
try {
return new URL(String(value)).origin;
} catch (error) {
return '[invalid URL]';
}
}
/**
@@ -128,9 +179,10 @@ function isEmptyOrNull(value) {
*
* @param {string} name 參數名稱。
* @param {*} value 參數值。
* @param {*} [displayValue=value] 寫進 log 的顯示值,敏感內容可先遮罩。
*/
function requireValue(name, value) {
info(`${name}=${value}`);
function requireValue(name, value, displayValue = value) {
info(`${name}=${displayValue}`);
if (isEmptyOrNull(value)) {
fail(`${name} is required`);
@@ -139,14 +191,52 @@ function requireValue(name, value) {
}
/**
* 驗證字串是否為非負整數
* 驗證字串是否為正整數,且落在安全整數範圍內;下限 1 可避免把保留數設成 0 而清空所有 release
*
* @param {string} name 參數名稱。
* @param {string} value 參數值。
*/
function requireInteger(name, value) {
if (!/^[0-9]+$/.test(value)) {
fail(`${name} must be a non-negative integer`);
function requirePositiveInteger(name, value) {
if (!/^[0-9]+$/.test(value) || !Number.isSafeInteger(Number(value)) || Number(value) < 1) {
fail(`${name} must be a positive integer within the safe integer range`);
process.exit(1);
}
}
/**
* 驗證值是否為合法的 HTTPS 絕對 URL,避免 URL 解析失敗留到主流程中途才拋出。
*
* @param {string} name 參數名稱。
* @param {*} value 參數值。
*/
function requireHttpsUrl(name, value) {
let parsed;
try {
parsed = new URL(String(value));
} catch (error) {
fail(`${name} must be a valid absolute URL`);
process.exit(1);
}
if (parsed.protocol !== 'https:') {
fail(`${name} must use HTTPS`);
process.exit(1);
}
}
/**
* 驗證 repository 是否為 `owner/repo` 格式且僅含安全字元,拒絕 `.`、`..` 等路徑片段。
*
* @param {string} name 參數名稱。
* @param {*} value 參數值。
*/
function requireRepository(name, value) {
const segments = String(value).split('/');
const isValidSegment = (segment) =>
/^[A-Za-z0-9_.-]+$/.test(segment) && segment !== '.' && segment !== '..';
if (segments.length !== 2 || !segments.every(isValidSegment)) {
fail(`${name} must be in owner/repo format`);
process.exit(1);
}
}
@@ -155,21 +245,35 @@ function requireInteger(name, value) {
* 對指定 URL 發送 request,回傳狀態碼與 body。
*
* @param {string} url 完整目標網址。
* @param {{ method?: string, headers?: Record<string, string> }} [options] request 設定。
* @param {{ method?: string, headers?: Record<string, string>, collectBody?: boolean }} [options] request 設定`collectBody` 為 `false` 時丟棄回應內容、只保留狀態碼
* @returns {Promise<{ statusCode: number, body: string }>} 回應狀態碼與內容。
*/
function requestJson(url, { method = 'GET', headers = {} } = {}) {
function request(url, { method = 'GET', headers = {}, collectBody = true } = {}) {
return new Promise((resolve, reject) => {
const target = new URL(url);
const client = target.protocol === 'http:' ? http : https;
if (target.protocol !== 'https:') {
reject(new Error(`Refusing to send request to non-HTTPS URL: ${target.origin}`));
return;
}
const req = client.request(
const req = https.request(
target,
{
method,
headers,
agent: keepAliveAgent,
},
(res) => {
const statusCode = res.statusCode || 0;
if (!collectBody) {
res.resume();
res.on('end', () => {
resolve({ statusCode, body: '' });
});
return;
}
const chunks = [];
res.setEncoding('utf8');
@@ -178,7 +282,7 @@ function requestJson(url, { method = 'GET', headers = {} } = {}) {
});
res.on('end', () => {
resolve({
statusCode: res.statusCode || 0,
statusCode,
body: chunks.join(''),
});
});
@@ -191,24 +295,35 @@ function requestJson(url, { method = 'GET', headers = {} } = {}) {
}
/**
* 逐頁抓取 JSON 陣列資料,直到回傳空頁為止。
* 逐頁抓取 JSON 陣列資料,直到回傳空頁為止;超過 `maxPages` 即中止並回報異常
*
* @param {string} baseUrl 不含 page 參數的 API URL。
* @param {Record<string, string>} headers request 標頭。
* @param {number} [maxPages=DEFAULT_MAX_PAGES] 分頁上限,可由環境變數 `MAX_PAGES` 覆寫。
* @returns {Promise<any[]>} 合併後的陣列資料。
*/
async function fetchAllPages(baseUrl, headers) {
async function fetchAllPages(baseUrl, headers, maxPages = DEFAULT_MAX_PAGES) {
const all = [];
for (let page = 1; ; page += 1) {
const pageUrl = `${baseUrl}?page=${page}`;
const { statusCode, body } = await requestJson(pageUrl, { headers });
if (statusCode < 200 || statusCode >= 300) {
throw new Error(`GET ${pageUrl} failed with HTTP ${statusCode}: ${body}`);
if (page > maxPages) {
throw new Error(`GET ${baseUrl} 分頁超過 ${maxPages} 頁上限,中止抓取以避免無限迴圈;資料量更大時可用 MAX_PAGES 環境變數調高上限`);
}
const pageUrl = `${baseUrl}?page=${page}`;
const { statusCode, body } = await request(pageUrl, { headers });
if (statusCode < 200 || statusCode >= 300) {
throw new Error(`GET ${pageUrl} failed with HTTP ${statusCode}: ${summarizeResponseBody(body)}`);
}
let data;
try {
data = JSON.parse(body || '[]');
} catch (error) {
throw new Error(`GET ${pageUrl} returned invalid JSON: ${summarizeResponseBody(body)}`);
}
const data = JSON.parse(body || '[]');
if (!Array.isArray(data)) {
throw new Error(`GET ${pageUrl} did not return a JSON array`);
}
@@ -231,40 +346,102 @@ async function fetchAllPages(baseUrl, headers) {
* @returns {Promise<{ statusCode: number, body: string }>} 回應狀態碼與內容。
*/
async function deleteResource(url, headers) {
return requestJson(url, {
return request(url, {
method: 'DELETE',
headers,
collectBody: false,
});
}
/**
* 執行 release 與 tag 清理流程
* 以固定批次大小處理項目,降低逐筆等待造成的延遲;單筆例外不會中止同批其他項目
*
* @param {any[]} items 要處理的項目。
* @param {number} batchSize 每批同時處理的數量。
* @param {(item: any) => Promise<boolean>} handler 單筆處理函式,回傳該筆是否成功。
* @returns {Promise<PromiseSettledResult<boolean>[]>} 依原始順序排列的處理結果。
*/
async function processInBatches(items, batchSize, handler) {
const results = [];
for (let index = 0; index < items.length; index += batchSize) {
const batch = items.slice(index, index + batchSize);
results.push(...(await Promise.allSettled(batch.map((item) => handler(item)))));
}
return results;
}
/**
* 彙總批次結果;記錄被 reject 的例外,並回傳是否有任何一筆失敗。
*
* @param {PromiseSettledResult<boolean>[]} results 批次處理結果。
* @returns {boolean} 只要有任一筆失敗即回傳 `true`。
*/
function hasBatchFailure(results) {
let failed = false;
for (const result of results) {
if (result.status === 'rejected') {
failed = true;
const reason = result.reason;
fail(`批次處理發生例外: ${reason instanceof Error ? reason.message : String(reason)}`);
} else if (result.value === false) {
failed = true;
}
}
return failed;
}
/**
* 執行 release 與 tag 清理流程;正式版與預發行版(prerelease)分組計算,各自保留最新 `KEEP_COUNT` 筆。
*/
async function main() {
const { GITEA_SERVER_URL, GITEA_REPOSITORY, RUNNER_TOKEN = '', KEEP_COUNT = '' } =
process.env;
const GITEA_SERVER_URL = normalizeEnvValue(process.env.GITEA_SERVER_URL);
const GITEA_REPOSITORY = normalizeEnvValue(process.env.GITEA_REPOSITORY);
const GITEA_TOKEN = normalizeEnvValue(process.env.GITEA_TOKEN) ?? '';
const KEEP_COUNT = normalizeEnvValue(process.env.KEEP_COUNT) ?? '';
const MAX_PAGES = normalizeEnvValue(process.env.MAX_PAGES) ?? '';
section('參數檢查');
requireValue('GITEA_SERVER_URL', GITEA_SERVER_URL);
requireValue('GITEA_SERVER_URL', GITEA_SERVER_URL, maskUrlForLog(GITEA_SERVER_URL));
requireHttpsUrl('GITEA_SERVER_URL', GITEA_SERVER_URL);
requireValue('GITEA_REPOSITORY', GITEA_REPOSITORY);
requireRepository('GITEA_REPOSITORY', GITEA_REPOSITORY);
requireValue('KEEP_COUNT', KEEP_COUNT);
requireInteger('KEEP_COUNT', KEEP_COUNT);
requirePositiveInteger('KEEP_COUNT', KEEP_COUNT);
let maxPages = DEFAULT_MAX_PAGES;
if (!isEmptyOrNull(MAX_PAGES)) {
info(`MAX_PAGES=${MAX_PAGES}`);
requirePositiveInteger('MAX_PAGES', MAX_PAGES);
maxPages = Number(MAX_PAGES);
}
const keepCount = Number(KEEP_COUNT);
const authHeaders = {};
if (isEmptyOrNull(RUNNER_TOKEN)) {
warn('RUNNER_TOKEN is empty; release API calls will be anonymous');
if (isEmptyOrNull(GITEA_TOKEN)) {
warn('GITEA_TOKEN is empty; release API calls will be anonymous');
} else {
info('RUNNER_TOKEN=[redacted]');
authHeaders.Authorization = `token ${RUNNER_TOKEN}`;
info('GITEA_TOKEN=[redacted]');
authHeaders.Authorization = `token ${GITEA_TOKEN}`;
}
const releaseApiUrl = `${GITEA_SERVER_URL}/api/v1/repos/${GITEA_REPOSITORY}/releases`;
const serverBase = new URL(GITEA_SERVER_URL);
serverBase.username = '';
serverBase.password = '';
serverBase.search = '';
serverBase.hash = '';
const serverBaseUrl = serverBase.toString().replace(/\/+$/, '');
const repositoryPath = GITEA_REPOSITORY.split('/').map(encodeURIComponent).join('/');
const releaseApiUrl = `${serverBaseUrl}/api/v1/repos/${repositoryPath}/releases`;
section('取得成品資訊');
info(`GET ${releaseApiUrl}`);
const releaseJson = await fetchAllPages(releaseApiUrl, authHeaders);
const releaseJson = await fetchAllPages(releaseApiUrl, authHeaders, maxPages);
releaseJson.sort((left, right) => {
if (left.created_at < right.created_at) {
return 1;
@@ -277,78 +454,101 @@ async function main() {
return 0;
});
const releaseCount = releaseJson.length;
info(`RELEASE_COUNT=${releaseCount}`);
const stableReleases = releaseJson.filter((item) => !item?.prerelease);
const preReleases = releaseJson.filter((item) => item?.prerelease);
info(`RELEASE_COUNT=${releaseJson.length}`);
info(`STABLE_COUNT=${stableReleases.length}`);
info(`PRERELEASE_COUNT=${preReleases.length}`);
info(`KEEP_COUNT=${KEEP_COUNT}`);
if (releaseCount <= keepCount) {
success('沒有需要清理的舊版本成品');
const releaseToKeep = [...stableReleases.slice(0, keepCount), ...preReleases.slice(0, keepCount)];
const releaseToDelete = [...stableReleases.slice(keepCount), ...preReleases.slice(keepCount)];
if (releaseToDelete.length === 0) {
info('沒有需要清理的舊版本成品');
} else {
section('刪除舊版本成品');
const releaseToDelete = releaseJson.slice(keepCount);
for (const releaseItem of releaseToDelete) {
if (!releaseItem || isEmptyOrNull(releaseItem.id)) {
warn(`略過沒有 id 的成品: ${releaseItem?.tag_name || ''} (${releaseItem?.name || ''})`);
continue;
const releaseResults = await processInBatches(releaseToDelete, DELETE_CONCURRENCY, async (releaseItem) => {
const releaseId = releaseItem?.id;
if (!Number.isSafeInteger(releaseId) || releaseId <= 0) {
fail(
`成品 id 不是正整數,視為資料異常: ${sanitizeLogText(releaseItem?.tag_name || '')} (${sanitizeLogText(releaseItem?.name || '')})`,
);
return false;
}
const releaseTag = releaseItem.tag_name || '';
const releaseName = releaseItem.name || '';
const deleteUrl = `${releaseApiUrl}/${releaseItem.id}`;
const releaseTag = sanitizeLogText(releaseItem.tag_name || '');
const releaseName = sanitizeLogText(releaseItem.name || '');
const deleteUrl = `${releaseApiUrl}/${releaseId}`;
info(`DELETE ${releaseTag} (${releaseName})`);
const { statusCode } = await deleteResource(deleteUrl, authHeaders);
if (statusCode === 204) {
success(`成功刪除: ${releaseTag} (${releaseName})`);
} else {
fail(`刪除失敗: ${releaseTag} (${releaseName}), HTTP ${statusCode}`);
info(`成功刪除: ${releaseTag} (${releaseName})`);
return true;
}
fail(`刪除失敗: ${releaseTag} (${releaseName}), HTTP ${statusCode}`);
return false;
});
if (hasBatchFailure(releaseResults)) {
throw new Error('至少有一筆 release 刪除失敗');
}
}
section('刪除未指定 release 的 tag');
const currentReleaseJson = await fetchAllPages(releaseApiUrl, authHeaders);
const releaseTags = new Set();
for (const item of currentReleaseJson) {
if (!isEmptyOrNull(item?.tag_name)) {
releaseTags.add(item.tag_name);
}
}
const releaseTags = new Set(
releaseToKeep
.map((item) => item?.tag_name)
.filter((tag) => !isEmptyOrNull(tag)),
);
const tagApiUrl = `${GITEA_SERVER_URL}/api/v1/repos/${GITEA_REPOSITORY}/tags`;
const tagApiUrl = `${serverBaseUrl}/api/v1/repos/${repositoryPath}/tags`;
info(`GET ${tagApiUrl}`);
const tagJson = await fetchAllPages(tagApiUrl, authHeaders);
const tagJson = await fetchAllPages(tagApiUrl, authHeaders, maxPages);
info(`TAG_COUNT=${tagJson.length}`);
for (const tagItem of tagJson) {
const tagResults = await processInBatches(tagJson, DELETE_CONCURRENCY, async (tagItem) => {
const tagName = tagItem?.name;
if (isEmptyOrNull(tagName)) {
warn('略過沒有名稱的 tag');
continue;
fail('tag 缺少名稱,視為資料異常');
return false;
}
const safeTagName = sanitizeLogText(tagName);
if (releaseTags.has(tagName)) {
info(`保留指定 release 的 tag: ${tagName}`);
continue;
info(`保留指定 release 的 tag: ${safeTagName}`);
return true;
}
const deleteUrl = `${tagApiUrl}/${encodeURIComponent(tagName)}`;
info(`DELETE tag ${tagName}`);
info(`DELETE tag ${safeTagName}`);
const { statusCode } = await deleteResource(deleteUrl, authHeaders);
if (statusCode === 204) {
success(`成功刪除未指定 release 的 tag: ${tagName}`);
} else {
fail(`刪除 tag 失敗: ${tagName}, HTTP ${statusCode}`);
info(`成功刪除未指定 release 的 tag: ${safeTagName}`);
return true;
}
fail(`刪除 tag 失敗: ${safeTagName}, HTTP ${statusCode}`);
return false;
});
if (hasBatchFailure(tagResults)) {
throw new Error('至少有一筆 tag 刪除失敗');
}
}
main().catch((error) => {
currentStage = '';
fail(error instanceof Error ? error.stack || error.message : String(error));
process.exit(1);
});
main()
.catch((error) => {
const showStack = process.env.RUNNER_DEBUG === '1';
fail(error instanceof Error ? (showStack && error.stack) || error.message : String(error));
process.exitCode = 1;
})
.finally(() => {
keepAliveAgent.destroy();
});