Conversation
fledge 1.8.0 was published to crates.io on 2026-09-19 from 435b7c5, a release-branch head that never reached main. 1.8.1 is that release cut from main, with #531, #533, #534 and #535 on top. Bumps Cargo.toml and flake.nix to 1.8.1. Cargo.lock differs from the published 1.8.0 lockfile only in fledge's own version; no dependency moves. The bump was done by hand, because `fledge release` runs `cargo generate-lockfile`, which re-resolves every dependency. The changelog section covers every commit since v1.7.2, with a note on 1.8.0. The stale "Unreleased" block, which described #520 (shipped here), is folded into that entry. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V3ZZAEiUP7xRJPozhZb6rL
0xLeif
requested review from
0xGaspar,
Kyntrin,
corvid-agent and
tofu-ux
and removed request for
a team
September 26, 2026 17:57
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
4 tasks
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
✅ Corvin says...
_
<(^\ .oO(Caw! ^v^)
|/(\
\(\\
" "\\
"Looking sharp! Like a beak should be."
CI Summary
| Check | Status |
|---|---|
| Dependency Audit | ✅ Passed |
| Integration (3 OS) | ✅ Passed |
| Lint (fmt + clippy) | ✅ Passed |
| Spec Validation | ✅ Passed |
| Tests (3 OS) | ✅ Passed |
Powered by corvid-pet
This branch has not been deployed
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.
Summary
main(260063a). It replaces the closed chore: release v1.8.0 #532 (v1.8.0).435b7c5(chore: release v1.8.0 #532's first head, never onmain; see.cargo_vcs_info.jsonin the crate). crates.io won't take 1.8.0 again, and a v1.8.0 tag onmainwould not match the published crate.corvid-stacktemplate's Trust pin: 1.2.0 → 1.2.1.Cargo.tomlandflake.nixare at 1.8.1.Cargo.lockdiffers from the published 1.8.0 crate's lockfile only in fledge's own version line.fledge release, which runscargo generate-lockfileand would re-resolve every dependency.[v1.8.1]section covers all 26 commits since v1.7.2, with a note on 1.8.0.## Unreleasedblock, which described Fix: lifecycle hooks could not work, two ways #520 (shipped here), into that entry (the other Codex P2).test (windows-latest)) is fixed by Fix: accept Windows' refused-connection wording in the isolation test #535 onmain.publishjob can run.CARGO_REGISTRY_TOKEN. As of 2026-09-26 it is missing. The repo has 0 Actions secrets, and the org shares onlyTAP_GITHUB_TOKEN. Without it, the tag'spublishjob fails loudly (by design, from Fix: publish to crates.io from the release workflow, and verify the registry #531) after the GitHub Release is built.435b7c5is a separate step. It would create a GitHub Release with binaries and a Homebrew bump for 1.8.0, so it's held for a decision.Test Plan
fledge lanes run verify(fmt, lint, test, build, spec-check, validate-templates) passes;fledge --version→fledge 1.8.1fledge trust verify --range origin/main..HEADpasses (augur: review, risk 46, from the lockfile and version-file churn)diffagainst the publishedfledge-1.8.0.crate'sCargo.lock: onlyfledge's version line differsv1.7.2..origin/mainappears in the[v1.8.1]section (26/26)testcells, the threeIntegrationcells, trust, spec-check, audit)🤖 Generated with Claude Code
https://claude.ai/code/session_01V3ZZAEiUP7xRJPozhZb6rL