Chore: release v1.1.2 - #26
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b8eec719f4
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| [plugin] | ||
| name = "trust" | ||
| version = "1.1.1" | ||
| version = "1.1.2" |
There was a problem hiding this comment.
When this commit is released as v1.1.2, the manual installation command in README.md still pins CorvidLabs/trust@v1.1.1, so users following the documented path will not receive this release or its SpecSync 5.2.0 update. This also makes bash tests/test.sh fail at the assertion on line 54 that the README tag matches plugin.toml; update the README pin alongside this version bump.
Useful? React with 👍 / 👎.
| [plugin] | ||
| name = "trust" | ||
| version = "1.1.1" | ||
| version = "1.1.2" |
There was a problem hiding this comment.
Once the README mismatch is fixed, the tagged Release workflow will still reach its strict SpecSync contract check with stale accepted evidence: CHG-0002's recorded acceptance manifest hashes the previous plugin.toml, and CHG-0003's manifest hashes the previous CHANGELOG.md, while this commit changes both without reopening and re-verifying those accepted changes. Earlier release records explicitly re-accepted these same governed inputs on each release tree, so refresh the lifecycle evidence before tagging v1.1.2.
AGENTS.md reference: AGENTS.md:L7-L7
Useful? React with 👍 / 👎.
| [plugin] | ||
| name = "trust" | ||
| version = "1.1.1" | ||
| version = "1.1.2" |
There was a problem hiding this comment.
Release this as 1.2.0 rather than 1.1.2 because the preceding change moves the public specsync-version input default from 5.1.1 to 5.2.0, changing the toolchain executed for consumers who omit that input. The repository's prior SpecSync upgrade explicitly documents this same kind of compatible public-default change as requiring a Trust minor release in .specsync/archive/changes/2026-07-18-CHG-0009-adopt-specsync-5-1-1-as-the-pinned-contract-toolchain/context.md, so classifying it as a patch breaks the established release-version contract for consumers and automation.
Useful? React with 👍 / 👎.
|
Superseded by a follow-up PR with the README tag fix included. |
1 participant
Summary
Test plan
fledge lanes run release(fmt, lint, test, spec) passed locally