Skip to content

[workflow-health] 15 stale lock files need recompilation — Apr 21, 2026 #27563

Closed as not planned

Description

@github-actions

Overview

15 workflow .md files have been modified more recently than their corresponding .lock.yml files, meaning the compiled workflows may not reflect the current source.

Affected Workflows

Workflow File
AI Moderator ai-moderator.md
Artifacts Summary artifacts-summary.md
Daily Compiler Quality daily-compiler-quality.md
Daily OTEL Instrumentation Advisor daily-otel-instrumentation-advisor.md
Daily Safe Output Integrator daily-safe-output-integrator.md
Deep Report deep-report.md
Developer Docs Consolidator developer-docs-consolidator.md
Functional Pragmatist functional-pragmatist.md
JS Sweep jsweep.md
Refactoring Cadence refactoring-cadence.md
Smoke Agent All None smoke-agent-all-none.md
Smoke Claude smoke-claude.md
Smoke Crush smoke-crush.md
Spec Enforcer spec-enforcer.md
Step Name Alignment step-name-alignment.md

Risk

Compiled behavior may not match source markdown. Workflows running from stale .lock.yml files may miss recent changes, security fixes, or configuration updates.

Resolution

Run make recompile to regenerate all lock files, then commit the result:

make recompile
git add .github/workflows/*.lock.yml
git commit -m "chore: recompile stale workflow lock files"

Context

  • Previous stale lock issue resolved via [aw] agentic workflows out of sync #27140 on Apr 20 — recurred after new workflow modifications.
  • Count: 0 stale on Apr 20 → 15 stale on Apr 21 (significant regression).

References: §24721544063

Note

🔒 Integrity filter blocked 1 item

The following item was blocked because it doesn't meet the GitHub integrity level.

  • #19099 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Workflow Health Manager - Meta-Orchestrator · ● 2.1M · ◷

  • expires on Apr 22, 2026, 12:20 PM UTC

Activity

  1. github-actions commented on Apr 21, 2026

    @github-actions
    ContributorAuthor

    🍪 Issue Monster selected this for Copilot!

    I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.

    If assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.

    Om nom nom! 🍪

    🍪 Om nom nom by Issue Monster · ● 8.4K · ◷

  2. Copilot commented on Apr 21, 2026

    Copilot
    Contributor

    The agent encountered an error and was unable to start working on this issue: Please try again later, or contact support if the problem persists. (Request id: 17C0:298521:7185B6:1C66ED0:69E7F193)

  3. github-actions commented on Apr 22, 2026

    @github-actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-04-22T12:20:57.532Z.

    Closed by Workflow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

cookieIssue Monster Loves Cookies!

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions