Skip to content

Chore: release v1.1.2 #26

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
0xLeif wants to merge 1 commit into from
Closed

Chore: release v1.1.2 #26

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,11 @@
# Changelog

## [v1.1.2] - 2026-07-27

### Changes

- bump pinned SpecSync to v5.2.0 (#25) (cc4244d)

## [v1.1.1] - 2026-07-18

> **Note:** The immutable `v1.1.0` tag is also void: its Release workflow
Expand Down
2 changes: 1 addition & 1 deletion plugin.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[plugin]
name = "trust"
version = "1.1.1"
version = "1.1.2"

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 27, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Update the documented install tag with the release version

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 👍 / 👎.

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 27, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Revalidate lifecycle evidence after generating the release

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 👍 / 👎.

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 27, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use a minor release for the public default change

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 👍 / 👎.

description = "One trust gate for contracts, verification, risk, and signed provenance"
author = "CorvidLabs"
license = "MIT"
Expand Down
Loading