chore(main): release 0.8.0

[github-actions]

🤖 I have created a release beep boop

0.8.0 (2026-08-16)

Features

• node,git: cap concurrent served git ops with a 503 load-shed (#62) (5981257)

Bug Fixes

• attest: use strict Ed25519 verification with regression test (1fcbbbd)
• ci: add tested release tag resolver (1b65f70)
• ci: recognize namespaced test attributes in pr-triage's needs-tests check (1989fcc)
• ci: reject unsafe release dispatch tags (7b365b0)
• ci: reject unsafe release dispatch tags (0b990d6)
• core: count distinct signer DIDs in certificate threshold check (3993fd1)
• core: Count distinct signer DIDs in certificate threshold check (50d3cbb)
• core: enforce strict RFC 8032 Ed25519 signature verification (425ebf4)
• core: use strict Ed25519 signature verification (a6c13be)
• git-remote: abort fetch on EOF without POSTing; harden the real-git test harness (#192) (1cb930c)
• git-remote: drive multi-round fetch as a v0 stateless-RPC client loop (#117) (5fdf155)
• git-remote: drive multi-round fetch as a v0 stateless-RPC client loop (#117) (a64b141)
• git-remote: normalize the shim's accepted socket to blocking (10e0840)
• git-remote: normalize the shim's accepted socket to blocking (#192) (8d7f95f)
• git-remote: reject malformed pkt-line length headers instead of flushing (8c04043)
• git-remote: skip content-free flush rounds in the fetch loop (#117) (68ba492)
• node: bind a peer row to its DID so only its keyholder can repoint it (#273) (8d38043)
• node: bound legacy readiness fallback (5af14c2)
• node: bound peer failure tracking (74f7554)
• node: count a completed fetch once per fetch, not per stateless-RPC POST (1c690c1)
• node: count fetch completion from the response outcome, not the request (5a5d4e1)
• node: Escape LIKE metacharacters in certificate prefix search (eeafa1f)
• node: Escape LIKE wildcards in certificate prefix search (96d8123)
• node: harden peer readiness state (6bd8f41)
• node: make metrics::init race-safe with Once (c45ec96)
• node: map ipfs/arweave DB outages to 503 via bare ? (#251) (0e2328b)
• node: map ipfs/arweave DB outages to 503 via bare ? (#251) (c29a91a)
• node: opaque AppError::Internal and AppError::Db HTTP bodies (#226) (241b366)
• node: opaque AppError::Internal and AppError::Db HTTP bodies (#226) (d192028)
• node: opaque GraphQL DB error messages (#250) (c10ccf1)
• node: preserve legacy peer compatibility (547f9ae)
• node: use readiness for peer liveness (225644a)
• node: use readiness for peer liveness (1a841a9)
• release: bump icaptcha-client with the rest of the workspace (6668525)
• repo_store: use SHA-256 for stable advisory-lock key (#210) (c380f9c)
• repo_store: use SHA-256 for stable advisory-lock key (#210) (89e10d0)
• review: assert the read-timeout postcondition and drop the socket clone (4d9bd5a)
• review: bound the probe's channel waits and stop overstating the handshake (d4e5ecf)
• review: make the LIKE escape independent of the SQL parser mode (1d3987b), closes #319
• test: match SHA-256 advisory-lock key in receive-pack deadline test (c68e1b0)

---

This PR was generated with Release Please. See documentation.

[euxaristia]

@coderabbitai full review

[coderabbitai]

⚠️ Action not completed

Review rate limited.

[coderabbitai]

Warning

Review limit reached

@euxaristia, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 7e8104f9-a9ef-4ea0-b6d6-bbaa020eaf98

📥 Commits

Reviewing files that changed from the base of the PR and between e4c7458 and e070bf2.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (8)

• .release-please-manifest.json
• CHANGELOG.md
• crates/git-remote-gitlawb/Cargo.toml
• crates/gitlawb-attest/Cargo.toml
• crates/gitlawb-core/Cargo.toml
• crates/gitlawb-node/Cargo.toml
• crates/gl/Cargo.toml
• crates/icaptcha-client/Cargo.toml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}