[aw] SelfCare / Docs Build Time: has stale lock file

Cerrado Apto para principiantes
  • ¿Algo no está bien?
#20,153 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
1/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
80/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions, yaml
Área
ci-cd

Línea de trabajo

Empieza con .github/workflows/self-care-docs-build-time-investigator.md y revisa el paso “Check workflow lock file” de la ejecución fallida si la causa no es evidente. Ejecuta gh aw compile y haz commit del archivo .lock.yml regenerado. Listo cuando el archivo lock compilado coincida con el código fuente del workflow.

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

Descripción

agentic-workflows
What happened

SelfCare / Docs Build Time has stale lock file.

View run #41638821449 · Workflow source · Previous failures

Branch: main

Next step

Review the failure details below for a targeted fix, or assign this issue to a coding agent to investigate.

Failure details

[!WARNING]
Lock File Out of Sync: The workflow could not start because its compiled lock file no longer matches the source markdown.

This means the workflow's .md file was edited but gh aw compile was not run afterwards to regenerate the corresponding .lock.yml file. The agent is prevented from running against a stale configuration to avoid unexpected behaviour.

To fix, recompile the workflow:

gh aw compile

Then commit and push the updated .lock.yml file.

More ways to recompile

Using the gh-aw MCP server (if configured):

{
  "tool": "compile",
  "arguments": {
    "validate": true
  }
}

Recompile all workflows at once:

gh aw compile --all

Verify the result:

gh aw compile --validate
How to investigate the mismatch

The workflow run logs contain a verbose debug pass that shows exactly what was hashed. Search the Check workflow lock file step logs for lines starting with [hash-debug] to see:

  • The raw frontmatter text that was used as input
  • Any imported files that were included in the hash
  • The canonical JSON that was fed to SHA-256
  • The resulting hash value

This makes it easy to spot accidental whitespace changes, encoding differences, or import path drift.

This mismatch can also happen on a fresh install (even without any manual edits) if gh aw add <path>@<ref> could not resolve the ref to an exact commit SHA during installation. In that case, rerun the add command with an exact SHA (or retry when API/rate-limit conditions recover), then recompile:

gh aw add <path>@<exact-sha>
gh aw compile
How to disable this check

[!CAUTION]
Disabling this check means the agent can run against an out-of-date compiled workflow. Only disable it if you have an alternative mechanism to keep lock files in sync.

Set stale-check: false in the on: section of your workflow frontmatter:

on:
  issues:
    types: [opened]
  stale-check: false

After editing, recompile the workflow: gh aw compile

Copy a debugging prompt

Paste this into your coding agent:

Debug the agentic workflow "self-care-docs-build-time-investigator" failure.
Follow https://raw.githubusercontent.com/github/gh-aw/main/debug.md
Failed run: https://github.com/githubnext/gh-cao/actions/runs/41638821449

If the repository includes the agentic-workflows skill, load it before investigating.

Manage failure notifications

To stop creating failure issues for this workflow, set this in its frontmatter and recompile:

safe-outputs:
  report-failure-as-issue: false

This only disables issue reporting; it does not fix the failure.

Generated from SelfCare / Docs Build Time · ◷

  • expires on Nov 4, 2026, 12:49 PM UTC
Lenguaje dominante
JavaScript
Estrellas
14
Forks
5
Merge medio
3 h 24 min
PR fusionados (30 d)
796

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 githubnext/gh-cao

Todos los issues de githubnext/gh-cao

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.