From 613b28baff22f91c3ee678550d311cd25598d0e6 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Tue, 29 Sep 2026 12:37:34 +0000 Subject: [PATCH] Version Packages --- .changeset/history-keeps-its-errors.md | 21 ------------ .changeset/loader-cache-stays-small.md | 28 --------------- CHANGELOG.md | 47 ++++++++++++++++++++++++++ package.json | 2 +- src-tauri/Cargo.lock | 2 +- src-tauri/Cargo.toml | 2 +- src-tauri/tauri.conf.json | 2 +- 7 files changed, 51 insertions(+), 53 deletions(-) delete mode 100644 .changeset/history-keeps-its-errors.md delete mode 100644 .changeset/loader-cache-stays-small.md diff --git a/.changeset/history-keeps-its-errors.md b/.changeset/history-keeps-its-errors.md deleted file mode 100644 index e846094..0000000 --- a/.changeset/history-keeps-its-errors.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -"fiber": patch ---- - -A response body that fails to load, or a history clear that fails, is reported -in the History tab again instead of vanishing the moment the tab opens. - -History now catches up with what the MCP server records whenever the tab is -opened, and a catch-up that succeeded cleared every error on the way — including -the one the tab was being opened to show. It now clears only an earlier failure -to list history, which is the one a successful list resolves. - -Also moves rustls to 0.23.45 for RUSTSEC-2026-0285, in which TLS 1.3 handshake -messages were accepted across encryption level boundaries, and fast-uri (used by -the editor's schema linting) to 3.1.8 for two advisories on how it parses a -URI's authority. - -Clicking another collection's settings cog while a settings drawer is open now -reliably switches to that collection. The click also counted as dismissing the -open drawer, and when the dismissal landed last the drawer closed and stayed -closed. diff --git a/.changeset/loader-cache-stays-small.md b/.changeset/loader-cache-stays-small.md deleted file mode 100644 index 75b5fa1..0000000 --- a/.changeset/loader-cache-stays-small.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -"fiber": patch ---- - -A collection whose OpenAPI schemas refer to each other in a ring no longer -writes a loader cache of gigabytes, and the MCP server no longer hangs on one. - -The cache stored every endpoint's request and response schema with each `$ref` -expanded in place, stopping only where a reference met itself on the current -path. Schemas that refer to each other — an operand that is an object or a -function, each of which holds operands — have a number of such paths that -grows factorially, and every endpoint got its own copy: one real collection's -cache reached 2.5 GB, a single endpoint's schema 252 MB. Every MCP call, down -to `list_sections`, read that file first, so the server answered `initialize` -and then nothing else. - -Schemas now live in a file of their own beside the endpoint list, stored as the -document wrote them, with each definition they reach kept once. An endpoint's -schema is put together when it is opened or asked for by `get_endpoint`, with -anything used more than once written a single time under `$defs` — which the -editor's linting already reads — so it can never be larger than the document it -came from. Listing, searching and deciding whether a call is allowed read only -the endpoint list. Request bodies built from such schemas are bounded too, -since a depth limit alone still let them branch into hundreds of kilobytes. - -A cache written by an earlier version still lists its endpoints straight away: -reading stops at the end of the endpoint list, before the schemas. Its schemas -are left unread until the next refresh writes both files. diff --git a/CHANGELOG.md b/CHANGELOG.md index f1322ac..bae2bff 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,52 @@ # fiber +## 0.16.3 + +### Patch Changes + +- [#102](https://github.com/MathiasWP/fiber/pull/102) [`69793d2`](https://github.com/MathiasWP/fiber/commit/69793d29a02be44d31f0ad46557908ab25d90b40) Thanks [@AndersRobstad](https://github.com/AndersRobstad)! - A response body that fails to load, or a history clear that fails, is reported + in the History tab again instead of vanishing the moment the tab opens. + + History now catches up with what the MCP server records whenever the tab is + opened, and a catch-up that succeeded cleared every error on the way — including + the one the tab was being opened to show. It now clears only an earlier failure + to list history, which is the one a successful list resolves. + + Also moves rustls to 0.23.45 for RUSTSEC-2026-0285, in which TLS 1.3 handshake + messages were accepted across encryption level boundaries, and fast-uri (used by + the editor's schema linting) to 3.1.8 for two advisories on how it parses a + URI's authority. + + Clicking another collection's settings cog while a settings drawer is open now + reliably switches to that collection. The click also counted as dismissing the + open drawer, and when the dismissal landed last the drawer closed and stayed + closed. + +- [#101](https://github.com/MathiasWP/fiber/pull/101) [`a0bf154`](https://github.com/MathiasWP/fiber/commit/a0bf154efc907d0ea3f7cb288bc80565fcbde221) Thanks [@AndersRobstad](https://github.com/AndersRobstad)! - A collection whose OpenAPI schemas refer to each other in a ring no longer + writes a loader cache of gigabytes, and the MCP server no longer hangs on one. + + The cache stored every endpoint's request and response schema with each `$ref` + expanded in place, stopping only where a reference met itself on the current + path. Schemas that refer to each other — an operand that is an object or a + function, each of which holds operands — have a number of such paths that + grows factorially, and every endpoint got its own copy: one real collection's + cache reached 2.5 GB, a single endpoint's schema 252 MB. Every MCP call, down + to `list_sections`, read that file first, so the server answered `initialize` + and then nothing else. + + Schemas now live in a file of their own beside the endpoint list, stored as the + document wrote them, with each definition they reach kept once. An endpoint's + schema is put together when it is opened or asked for by `get_endpoint`, with + anything used more than once written a single time under `$defs` — which the + editor's linting already reads — so it can never be larger than the document it + came from. Listing, searching and deciding whether a call is allowed read only + the endpoint list. Request bodies built from such schemas are bounded too, + since a depth limit alone still let them branch into hundreds of kilobytes. + + A cache written by an earlier version still lists its endpoints straight away: + reading stops at the end of the endpoint list, before the schemas. Its schemas + are left unread until the next refresh writes both files. + ## 0.16.2 ### Patch Changes diff --git a/package.json b/package.json index 7ace09e..b9bc1d4 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "fiber", "private": true, - "version": "0.16.2", + "version": "0.16.3", "type": "module", "packageManager": "pnpm@11.22.0", "engines": { diff --git a/src-tauri/Cargo.lock b/src-tauri/Cargo.lock index eb6487e..b42dc5c 100644 --- a/src-tauri/Cargo.lock +++ b/src-tauri/Cargo.lock @@ -1354,7 +1354,7 @@ dependencies = [ [[package]] name = "fiber" -version = "0.16.2" +version = "0.16.3" dependencies = [ "base64 0.23.1", "chacha20poly1305", diff --git a/src-tauri/Cargo.toml b/src-tauri/Cargo.toml index 7945a7d..c706d87 100644 --- a/src-tauri/Cargo.toml +++ b/src-tauri/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "fiber" -version = "0.16.2" +version = "0.16.3" description = "A local-first API client" authors = ["Mathias Picker"] license = "MIT" diff --git a/src-tauri/tauri.conf.json b/src-tauri/tauri.conf.json index 696c21d..247c888 100644 --- a/src-tauri/tauri.conf.json +++ b/src-tauri/tauri.conf.json @@ -1,7 +1,7 @@ { "$schema": "../node_modules/@tauri-apps/cli/config.schema.json", "productName": "Fiber", - "version": "0.16.2", + "version": "0.16.3", "identifier": "dev.fiber.app", "build": { "frontendDist": "../build",