ci(openspec): pin the OpenSpec CLI to 1.13.1 (verbara-meta/ADR-0022) - #110
Merged
Merged
Conversation
Same-shaped PR of the ADR-0022 rollout; the Sdk pilot is 14/14 green. The pin moves because a remedy this workspace prescribes does not run. verbara-meta/ADR-0019 carried `retire_capabilities: true` into every repo's openspec/config.yaml; it aborts on any spec whose scenario bullets wrap onto a second line, which is 34 of the ecosystem's 51 living specs, and 1.13.0 is the first release where it works. 1.13.1 additionally stops config.yaml's `context`/`operations.*.guidance` being printed raw into the agent instruction envelope, closes ReDoS in update/archive, and stops a repo .npmrc redirecting the CLI's update check. This repo's tree is green under both pins (`No items found to validate` — rc=0), so CI is the acceptance test and the revert is this one line. decision_ref: verbara-meta/ADR-0022
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
verbara-website | 3567d1c | Commit Preview URL Branch Preview URL |
Sep 20 2026, 02:20 PM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
decision_ref:verbara-meta/ADR-0022— OpenSpec CLI pin: 1.8.0 → 1.13.1 (supersedes ADR-0018).Same-shaped PR of the ADR-0022 rollout. The pilot, Verbara.Sdk#276, is 14/14 green.
The diff
One line. The revert is the same line.
Why (the ADR carries the full argument; this is the short form)
retire_capabilities: trueinto every repo'sopenspec/config.yaml. It aborts on any spec whose scenario bullets wrap onto a second line — 34 of the ecosystem's 51 living specs — and 1.13.0 (#1782) is the first release where it works.config.yaml'scontextandoperations.*.guidanceraw into the agent instruction envelope. 1.13.1 (#1902) escapes both, closes catastrophic regex backtracking inupdate/archive, and stops a repo.npmrcpointing the update check at an attacker-controlled registry — which everynpx -yin every PR runs.This repo is green under both pins
validate --all --strict --no-interactiveNo items found to validate— rc=0No items found to validate— rc=0This repo carries no
openspec/tree content, so the job is a no-op at both versions. The pin still moves: the line is a fact-registry fact/xr:doctorcompares across repos, and a lone 1.8.0 among four 1.13.1 is drift.What to expect after this lands
The first
openspec archiveunder the new pin reformats every living spec it touches — a blank line either side of## Requirements, and the file's trailing blank line dropped.+2 / -1blank lines per touched spec, zero content change, verified across 28 specs in ADR-0022's Gate 2. Cosmetic and one-time per spec; do not read it as corruption.