chore: release new version 🚀

CHANGELOG.md

@@ -1,5 +1,32 @@
 # nostream
 
+## 3.12.0
+
+### Minor Changes
+
+- [#1034](https://github.com/cameri/nostream/pull/1034) [`e410a75`](https://github.com/cameri/nostream/commit/e410a759cc126e01ce0b198c670d828807762448) Thanks [@Ferryx349](https://github.com/Ferryx349)! - feat(peering): treat authenticated peers as feeds, not clients
+
+  Adds `limits.peer`, a separate limit set for connections that have proven a
+  configured `peering.peers` pubkey with NIP-42 AUTH. Peer subscriptions use
+  `limits.peer.subscription` instead of `limits.client.subscription`, and peer
+  messages use `limits.peer.message` in a separate rate-limit bucket, so a
+  full-feed subscription cannot trip the client EWMA limiter or the client
+  `max_subscriptions` cap.
+
+  Peers are eligible for full feeds by default: `maxLimit` is uncapped and the
+  subscription caps are higher. An omitted peer REQ `limit` queries the full
+  stored feed instead of the client 500-event default, and peer filter counts are
+  not rejected by the protocol's former fixed ten-filter cap. Raw filter counts are
+  still bounded before deduplication, and stored reads wait for the socket's
+  send-flush callback so a slow peer cannot grow worker memory. Deleted and expired rows
+  are excluded in SQL before the limit, so they cannot consume a page slot.
+
+  A high but finite peer message rate keeps the credential from becoming an
+  unbounded egress path. Unauthenticated or unconfigured connections keep the
+  existing client limits exactly as before. The new limits are validated with the
+  rest of the settings document and documented in `CONFIGURATION.md` and
+  `docs/PEERING.md`.
+
 ## 3.11.0
 
 ### Minor Changes

package.json

@@ -1,6 +1,6 @@
 {
   "name": "nostream",
-  "version": "3.11.0",
+  "version": "3.12.0",
   "packageManager": "pnpm@10.33.0",
   "private": true,
   "description": "A Nostr relay written in Typescript.",