Skip to content

chore: release v1.8.1 #536

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

Open
0xLeif wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: release v1.8.1 #536

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
55 changes: 52 additions & 3 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,12 +5,61 @@ All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## Unreleased
## [v1.8.1] - 2026-09-26

> **About 1.8.0.** fledge 1.8.0 was published to crates.io on 2026-09-19 from `435b7c5`, a release-branch commit that never reached `main`. 1.8.1 is that release cut from `main`. Everything below shipped in 1.8.0 except #531, #533, #534 and #535. The one difference in the binary is the `corvid-stack` template's Trust pin: 1.2.0 in 1.8.0, 1.2.1 here (#533). Dependencies are unchanged from 1.8.0.

### CI

- pin SpecSync Action to @v6 with version 6.0.0 (#516) (78b017b)
- pin Trust to v1.2.0-rc.4 and SpecSync to 6.0.0-rc.12 (#514) (ecaf8a3)

### Changes

- the diamond-deps change declares `main`, the spec that owns src/main.rs (#524) (41430ed)
- pin Trust 1.2.0 and SpecSync 6.0.0 (#515) (3c68992)

### Chores

- pin Trust 1.2.1 (#533) (6221e1d)
- archive fix-diamond — the SDD ledger is now empty (#530) (31d5f45)
- close the last two SDD records (#529) (49f2269)
- close out the SDD ledger — audit passes, 0 stale (#527) (fc9f5a8)
- land the depth-bound change's SpecSync evidence (#526) (d3d710b)

### Features

- A plugin that declares a lifecycle hook now keeps the capabilities it was granted. Capabilities were recorded only for protocol plugins, so a plain command plugin's hooks were dead on arrival: `exec` was prompted for at install, the grant discarded, and every hook skipped silently thereafter.
- Lifecycle hooks are told which repository they fired for, via `FLEDGE_REPO_ROOT`. A hook runs with its working directory set to the plugin's own source directory, so until now a `post_work_start` or `pre_push` hook had no way to inspect the project it was reacting to. The variable is always set: the repository root, the working directory outside a repository, or `.` if even that cannot be read.
- high-level design doc with Mermaid diagrams (#534) (c65af7f)
- opt-in --stream for live task output (#507) (#509) (28a5bba)
- fledge spec lint — quality gate for the spec itself (#429) (#505) (bfe917c)
- add root-level action.yml GitHub Action for installing fledge in CI (#511) (da1c68a)
- the hi habit, so intent gets written before the work (#519) (4196958)

### Fixes

- accept Windows' refused-connection wording in the isolation test (#535) (260063a)
- publish to crates.io from the release workflow, and verify the registry (#531) (7214df6)
- upgrade Astro 5 to 7, clearing ten Dependabot advisories (#528) (9c02041)
- bound task-graph walk depth so a deep chain errors instead of aborting (#525) (38ba621)
- a diamond dependency is a DAG, not a cycle (#508) (#513) (f659d69)
- make the hooked-plugin regression test actually guard the bug (#521) (fbf51a9)
- AGENTS.md told agents not to do what this repo just did (#523) (57155c0)
- lifecycle hooks could not work, two ways (#520) (c4abcb2)
- A plugin that declares a lifecycle hook now keeps the capabilities it was granted. Capabilities were recorded only for protocol plugins, so a plain command plugin's hooks were dead on arrival: `exec` was prompted for at install, the grant discarded, and every hook skipped silently thereafter.
- Lifecycle hooks are told which repository they fired for, via `FLEDGE_REPO_ROOT`. A hook runs with its working directory set to the plugin's own source directory, so until now a `post_work_start` or `pre_push` hook had no way to inspect the project it was reacting to. The variable is always set: the repository root, the working directory outside a repository, or `.` if even that cannot be read.
- archive the five stranded accepted SDD records (#506) (c4b06f1)

### Other

- Adopt hi: record what fledge should be, as 197 criteria (#518) (089c68d)

### Refactoring

- name the two remaining --json schema literals (#444) (#503) (6eb7a3e)

### Tests

- mocking harness + $HOME isolation + publish coverage (#447) (#504) (43a2138)

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

Expand Down
Loading
Loading