🚀 Lock workflow dependencies with GitHub's actions.lock

Aberta
#33 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

@coconux3 já está trabalhando nisso.

Desde 11/11/2026.

Avaliação

Dificuldade
2/5
Tempo estimado
1-3 horas
Facilidade para iniciantes
30/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
github-actions
Domínio
ci-cd, security

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

🔖 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?
Linguagem predominante
TypeScript
Estrelas
8
Forks
3
Merge médio
2h 9min
PRs com merge (30d)
6

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de appwrite/docker-browser

Todas as issues de appwrite/docker-browser

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.