Feature request: upgrade action versions and regenerate actions.lock

Abierto
  • ¿Algo no está bien?
#140 0 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github-actions, go
Área
cli, devops, security

Línea de trabajo

Start by reviewing PR #30 and the current distinction between --relock and updating YAML action references. Define the upgrade operation's scope for workflow and local composite-action references, including transitive lock entries, and consider how the YAML and actions.lock changes should be validated.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area:cli feature-request

Summary

Would it be possible to add a local upgrade operation that updates action version tags in YAML and regenerates actions.lock in one invocation?

Current behavior

--relock refreshes locked SHAs for existing mutable refs. It does not select newer version tags or update uses: references.

Upgrading to a newer version therefore requires updating the YAML references separately before regenerating the lockfile.

Expected behavior

An upgrade operation would:

  • Update action version references in workflows and local composite actions.
  • Keep readable version tags in YAML, with resolved commit SHAs in actions.lock.
  • Regenerate the affected lock entries, including the required transitive dependencies.

For example, upgrading actions/[email protected] to actions/[email protected] would update both the YAML reference and the corresponding lock entries.

Related context

PR #30 removed the previous update command during the transition to a detached lockfile and mentioned adding it separately.

Would a local upgrade operation still fit the intended scope of the project?

Lenguaje dominante
Go
Estrellas
253
Forks
15
Merge medio
19 h 30 min
PR fusionados (30 d)
60

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/gh-actions-lock

Todos los issues de github/gh-actions-lock

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.