🚀 Lock workflow dependencies with GitHub's actions.lock
維護者通常 1 天內回覆
@coconux3 已經在處理了。
開始於 2026年11月11日。
評估
- 難度
- 2/5
- 預估耗時
- 1-3 小時
- 新手友好度
- 30/100
研究方向
Review the workflows in .github/workflows/ and the proposed fork comparison linked in the issue to see which actions need locking. Start with the official workflow dependency lockfile documentation and the gh actions-lock command. Done means .github/workflows/actions.lock is added and records the workflow action commits; the issue says Renovate will keep it updated.
由索引模型根據 Issue 內容生成。
描述
🔖 Enhancement description
Add GitHub's workflow dependency lockfile (.github/workflows/actions.lock, generated with gh actions-lock) to this repo. It records the commit behind every action the workflows use, so a moved tag can't change what runs.
🎤 Pitch
release.yml pushes appwrite/browser to Docker Hub with DOCKERHUB_TOKEN, through five actions on mutable tags (docker/login-action@v3, docker/build-push-action@v5, ...). That image runs in every self-hosted Appwrite (appwrite/browser:0.3.10 in docker-compose). If one of those tags moves, the new code runs with the token.
GitHub's lockfile is the official way to lock actions, and it also locks what these actions pull in: https://docs.github.com/actions/concepts/security/workflow-dependency-lockfiles. Renovate keeps actions.lock in sync on each action update: https://docs.renovatebot.com/modules/manager/github-actions/#github-actions-lockfile-actionslock. It would cover what #31 does with SHA pins.
Per your contributing guide, no PR without an assigned issue: the change is ready on a fork so you can see the end result: https://github.com/coconux3/appwrite-docker-browser/compare/main...cicd-33-lock-workflow-dependencies
👀 Have you spent some time to check if this issue has been raised before?
- I checked and didn't find similar issue
🏢 Have you read the Code of Conduct?
- I have read the Code of Conduct
- 主要語言
- TypeScript
- 星號
- 8
- 分支
- 4
- 平均合併
- 2 小時 9 分鐘
- 30 天內合併 PR
- 6
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
appwrite/docker-browser 的其他 Issue
-
難度 4/5 3-5 天 新手友好度 25/100
appwrite/docker-browser#29 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 15/100
appwrite/docker-browser#22 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 3/5 1-2 天 新手友好度 68/100
appwrite/docker-browser#20 ·
維護者通常 1 天內回覆
-
documentation
難度 2/5 1-3 小時 新手友好度 52/100
appwrite/docker-browser#15 ·
維護者通常 1 天內回覆
查看 appwrite/docker-browser 的全部 Issue
相似的 Issue
-
難度 1/5 1 小時以內 新手友好度 95/100
marimo-team/marimo#11949 ·
維護者通常 1 天內回覆
-
bug server-time v2
難度 2/5 1-3 小時 新手友好度 76/100
modelcontextprotocol/servers#5559 ·
維護者通常 1 天內回覆
-
bug
難度 1/5 1 小時以內 新手友好度 88/100
Monsieur-Nico/textConvert#479 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 82/100
router-for-me/Home-Management-Center#232 ·
維護者通常 1 天內回覆
-
clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster maturity:stable P3
難度 2/5 1-3 小時 新手友好度 72/100
openclaw/openclaw#200937 · 1 則留言 · 1 個 reaction ·
維護者通常 1 天內回覆