Skip to content

Releases

v1.6.0

Choose a tag to compare

@ip-releaser ip-releaser released this 24 Oct 01:36
8c04e03

What's Changed

Full Changelog: v1.5.0...v1.6.0

v1.5.0

Choose a tag to compare

@ip-releaser ip-releaser released this 23 Oct 18:46
6a9fb08

What's Changed

  • feat(public-bundle): add classification reader, bundle builder and privacy check by @kraigparkinson in #63
  • fix(public-bundle): match Vercel links by exact host; record the host-matching learning by @kraigparkinson in #64
  • feat(public-bundle): add the reusable publish workflow, catalog generator and publisher by @kraigparkinson in #65
  • feat(public-bundle): add the catalog integrity check and its reusable workflow by @kraigparkinson in #66
  • feat(ci): release on every merge to main by @kraigparkinson in #67

Full Changelog: v1.4.0...v1.5.0

v1.4.0

Choose a tag to compare

@kraigparkinson kraigparkinson released this 15 Oct 21:33
4be842a

validate-plugin-manifest now checks Claude's plugin upload limits (#62). New input upload-limits: error | warn | off (default error).

v1.3.0 — reusable-git-ai-notes.yml carries Git AI notes across squash-merges

Choose a tag to compare

@kraigparkinson kraigparkinson released this 18 Sep 01:23
b0caf38

Added

  • reusable-git-ai-notes.yml rewrites Git AI attribution notes (refs/notes/ai) onto squash-merge commits, so attribution reaches main. git-ai is pinned by version and SHA-256, cross-checked against the release's SHA256SUMS, and verified by build-provenance attestation before it runs. Needs contents: write on the calling job and no secrets. Decision: devops-excellence ADR-095 (#55).

No change to any existing reusable.

v1.2.0 — the five private-only tier-1 reusables land on the public host

Choose a tag to compare

@kraigparkinson kraigparkinson released this 09 Sep 21:34
260938f

Ports the five reusables that existed only on the private devops-excellence host, completing ADR-084 Stage B (devops-excellence#611).

A public or internal repo cannot resolve a reusable workflow hosted in a private repo — the call dies at startup_failure with zero jobs and no logs. These five were unreachable to every public and internal consumer until now.

New reusables

Reusable Purpose Declared secrets
reusable-ci-node.yml typecheck / build / test for Node projects (pnpm or npm) NODE_AUTH_TOKEN (optional)
reusable-codeql.yml CodeQL analysis — see the adoption blocker below none
reusable-claude-code-review.yml Claude Code auto-review on PRs CLAUDE_CODE_OAUTH_TOKEN (optional)
reusable-architecture-fitness.yml the caller's fitness:self self-compliance suite NODE_AUTH_TOKEN (optional)
reusable-bdd.yml the caller's offline Cucumber suite via its bdd script NODE_AUTH_TOKEN (optional)

All ten reusables on this host are now reachable at @v1.

Credential surface

Identical to the private copies for all five. None reads a 1Password PEM or mints a GitHub App token, so the ADR-065 whole-vault hazard does not attach to any of them — that lives in reusable-auto-merge.yml, which was already public and already carries the scoped OP_*_PUBLIC_TOKEN form. No secrets.OP_SERVICE_ACCOUNT_TOKEN expression appears in any copy.

Each file's header now carries a Credential surface section and a Declared delta from the private copy section, per the new RWF-005.

Adoption blocker for reusable-codeql

Verified by a witnessed run on this public repo: the reusable works — it resolves, initializes, autobuilds and analyzes — and its SARIF upload is then rejected while code scanning default setup is enabled on the consumer repo. Default setup and advanced setup are mutually exclusive.

Measured 2026-09-09, every active public repo in the org and all five tier-1 private repos have default setup configured, so reusable-codeql currently has no repo it can succeed on. This predates the port. The org-wide decision is devops-excellence#664. Read the file's header before wiring it.

Fix

reusable-ci-node.yml — the three npm-branch ::error:: messages interpolated a live secrets expression where they meant to print a literal, splicing the real registry token into the annotation (masked as ***, which is why it went unnoticed). The pnpm branches in the same file were already correct. The private copy still carries the defect: devops-excellence#661.

Upgrading

Nothing breaks. Consumers pinned at @v1 pick this up automatically once the v1 alias moves. No input, secret, or permission contract changed on any previously-released reusable.

v1.1.0

Choose a tag to compare

@kraigparkinson kraigparkinson released this 04 Sep 01:57
237d43f

Adds reusable-release-please.yml to the public host, so internal and public callers can reach it. Previously it existed only on the private devops-excellence host, which an internal caller cannot resolve — the call fails at startup with zero jobs and no logs.

Added

  • reusable-release-please.yml (#44) — ported from devops-excellence/.github/workflows/reusable-release-please.yml@v1 (18de53b), preserving the workflow_call input and secret surface so existing private callers migrate with a one-line uses: change. Mints an ip-releaser App token rather than falling back to GITHUB_TOKEN, which the enterprise can_approve_pull_request_reviews: false policy blocks from creating the Release PR.
  • docs/adr/RWF-004 — records why the port keeps the vault-wide 1Password token instead of the scoped one its siblings use, and bars public callers until that is superseded.

Fixed

  • README (#45) — the visibility restriction was stated for public callers only. It now reads in caller-visibility terms: a private host is reachable only by private same-org callers, and access_level: organization does not change that.

Consumers

@v1 fast-forwards to this release. Internal and private callers are in scope; public callers should not wire this reusable yet — see RWF-004 clause 2.

v1.0.3

Choose a tag to compare

@kraigparkinson kraigparkinson released this 13 Aug 16:54
17aab19

What's Changed

  • fix(auto-merge): stop resolve_once from leaking partial stdout on a genuine gh api failure by @kraigparkinson in #38
  • feat(auto-merge): route close-linked-issues resolve step through ip-org-auditor by @kraigparkinson in #39

Full Changelog: v1.0.2...v1.0.3

v1.0.2

Choose a tag to compare

@kraigparkinson kraigparkinson released this 11 Aug 00:14
c0f8ccc

What's Changed

  • ci: lint this repo's own workflows with actionlint + shellcheck by @kraigparkinson in #25
  • docs(agents): consume the canonical triage vocabulary instead of forking it by @kraigparkinson in #34
  • docs(adr): initialize adr-tools and backfill the @v1 versioning decision by @kraigparkinson in #26
  • fix(auto-merge): end red when auto-merge fails to arm by @kraigparkinson in #35
  • fix(automerge): port close-linked-issues job for tier3 (devops-excellence#519) by @kraigparkinson in #37

Full Changelog: v1...v1.0.2

v1.0.1

Choose a tag to compare

@kraigparkinson kraigparkinson released this 27 Jul 22:56
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.

v1.0.0

Choose a tag to compare

@kraigparkinson kraigparkinson released this 21 Jul 05:53
3566b22

Initial release establishing the @v1 semver contract for this repo's reusable workflows and the read-pem-from-1p composite action.

Consumers should pin the moving major alias:

uses: Integral-Productivity/reusable-workflows/.github/workflows/<name>.yml@v1

@v1 always points at the latest v1.x.y release and auto-inherits non-breaking fixes; a breaking change ships as v2. See the README "Versioning" section and devops-excellence ADR-046.

This release bootstraps the moving v1 alias (maintained henceforth by major-tag-mover.yml).