Repository navigation
chore(main): release 0.8.0 - #307
github-actions[bot] wants to merge 2 commits into
Conversation
1ad36b8 to
bd90b46
Compare
552af21 to
0e19676
Compare
|
@coderabbitai full review |
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
c2ded5b to
3810499
Compare
euxarist
left a comment
There was a problem hiding this comment.
Mechanically this is clean: pure version bumps (0.7.1 to 0.8.0 across the manifests and lockfile, including the long-owed icaptcha-client alignment), a generated changelog, no workflow edits, no checkout or token changes, CI green, and main has not moved past the changelogged commit. No migration-number conflicts with the in-flight PR stacks (those claim v27+; this touches none).
The question I want on the record before this is merged is a release-risk one: v0.8.0 would ship with eight open sev:high issues unfixed on main: #469 (uncapped anonymous Kademlia resolution), #470 (unbounded ref-update notify fields), #471 (encrypted-blob serving with no size cap), #484 (anonymous unbounded PR diffs), #485 (stats loads the full inventory per request), #487 (Tigris cold-acquire RAM buffering), #491 (silent identity regeneration), and #492 (DID-control not proven at registration). It also carries a BREAKING CHANGE (owner-only push default). None of these have open fix PRs except via the #462-#466 stack. If shipping them in 0.8.0 is an accepted risk, fine; if not, this release is worth holding until the in-flight bounds work lands. Whoever merges should make that call explicitly rather than by default.
9c4cb35 to
7f7e2b0
Compare
e54895e to
91bc34c
Compare
🤖 I have created a release beep boop
0.8.0 (2026-11-06)
⚠ BREAKING CHANGES
git-receive-packnow rejects a push whose authenticated DID is not the repo owner, returning 403 before any ref update is applied. Delegated and CI keys count as non-owners: a UCANgit/pushcapability is verified but not yet honored for authorization, so an agent pushing under its own DID cannot push while this is on. SetGITLAWB_ENFORCE_OWNER_PUSH=falseduring a rolling upgrade, or have automation push as the repo owner, until scoped collaborator / UCAN-delegated push rights land.Features
Bug Fixes
This PR was generated with Release Please. See documentation.