Skip to content

v1.0.1

Choose a tag to compare

@kraigparkinson kraigparkinson released this 27 Jul 22:56
· 23 commits to main since this release
92bf59c

Non-breaking. @v1 moves to this release, so consumers inherit it automatically with no caller change required.

reusable-promote-stable.yml now requests only contents: read (#15)

If your caller declares permissions: contents: write, nothing breaks — keep it or drop it. A caller may grant more than the reusable requests. What changes is that a caller now needs no permissions: block at all.

Why it mattered: a called reusable cannot request greater permissions than its caller grants, and both this org and its repos default default_workflow_permissions to read. While this workflow declared contents: write, every thin caller was obliged to declare a matching block — and without one, GitHub rejected the workflow graph at compile time: startup_failure, 0 jobs, no logs, which reads like an outage rather than a config error.

Two properties made that unusually costly:

  • It stays latent. promote-stable only fires on a release tag, so a broken caller looks healthy indefinitely.
  • It fails in the wrong direction. The tag and GitHub Release are created normally, so a release looks shipped — while stable, the ref the marketplace tracks, never advances.

holacracy-claude-plugin lost a release to this: v0.10.0 was tagged and published while stable stayed 20 commits and five features behind, and recovery required cutting v0.10.1, because a tag-triggered workflow resolves its definition from the pushed ref (the failed run cannot simply be re-run). Three more consumers were latent with the same gap. All four have since been fixed caller-side; this release removes the requirement rather than documenting the footgun.

The write was never needed: actions/checkout is handed the ip-releaser App token explicitly and the fast-forward push authenticates with those persisted App credentials, so no step uses GITHUB_TOKEN for a write. The header's canonical example previously omitted the permissions: block and so kept minting broken callers; it now states the requirement is nil, with a note for anyone pinned to an earlier @v1.

Recommended action: none required. If you want the tidier caller, delete permissions: contents: write from your promote-stable.yml — but only once you are on this release or later.

docs/agents/triage-labels.md added (#16)

This repo carried three of the five canonical triage labels, so an agent asked to triage issues here improvised silently. Adds the identity mapping at the same path the sibling repos use, plus the two missing labels (needs-triage, needs-info) and guidance that shared-reusable changes and releases lean ready-for-human. Docs and labels only — no workflow behavior.