[cpitzi]

Closes #265. Supersedes Dependabot's #228.

What changes

• Three caller pins move from @v1.4.0 to @v1.6.0:

  • .github/workflows/claude.yml (claude-responder.yml)
  • .github/workflows/shellcheck.yml
  • .github/workflows/tf-lint.yml

  With Add the agent-pr-gate caller and move docs-check to v1.6.0 (lentago/.github#289) #264's docs-check.yml and agent-pr-gate.yml, five of the six shared-workflows callers are now on v1.6.0.

• README "Shared reusable workflows" row. It said docs-check.yml wraps …/docs-check.yml@main, but that caller has been tag-pinned since v1.4.0 (raised in Add the agent-pr-gate caller and move docs-check to v1.6.0 (lentago/.github#289) #264's review). The row now describes every workflow except terraform.yml as a thin caller pinned to a release tag and kept current by Dependabot. It names no tag, so it won't go stale on the next bump.

Why

After #264 moved docs-check to v1.6.0, the repo's callers sat on three tags. Dependabot's #228 (v1.4.0 → v1.5.0 for four callers) now conflicts on the docs-check line. Bumping the remaining three straight to v1.6.0 resolves both; Dependabot should close #228 as up to date once this merges.

Scope and trade-offs

• No caller inputs, secrets or permissions change.
  • v1.5.0 bumped claude-code-action, which the responder uses.
  • v1.6.0's notes say these three callers "have nothing to change" and differ from v1.5.1 only in the internal render-claude-summary ref.
• claude-review.yml stays at @v1.5.0. A PR that changes the reviewer's own caller workflow makes claude-code-action skip, so it would get a "not a review" notice instead of a review. That one-line bump goes in its own PR with a local review.
• No Terraform files. The terraform gate skips the plan.

🤖 Generated with Claude Code

[github-actions]

Review (haiku, claude-review.yml)

No significant problems found. The diff only moves three workflow caller pins from @v1.4.0 to @v1.6.0 and rewrites one README table row. It touches no Terraform, so the apply blast radius is zero. Every caller stays tag-pinned, permissions and inputs are unchanged, and the README row now matches the files in .github/workflows. The PR body has Closes #265, the title matches the body, and the body carries a full summary. I could not confirm from this environment that the v1.6.0 tag in lentago/shared-workflows contains the reusable workflows the PR relies on, so that check is still open.

[cpitzi]

Triage of the Haiku review: no findings. The one open check is confirmed:

• claude-responder.yml, shellcheck.yml and tf-lint.yml all exist at lentago/shared-workflows@v1.6.0. The contents API at ref=v1.6.0 returns blob SHAs a50d776, 732385a and 3345d4f.
• The shellcheck / shellcheck and tf-lint / tf-lint checks on this PR already ran green from the v1.6.0 callers.
• The responder runs only on issue and PR comments, so this PR does not exercise it.

Arming.