Skip to content

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.