From a28631e3afe2921905ba7a54f1aa6c70a51d83e9 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Mon, 24 Aug 2026 15:47:43 +0000 Subject: [PATCH] Version Packages --- .changeset/history-knows-its-collection.md | 11 ----------- .changeset/select-by-section-too.md | 11 ----------- CHANGELOG.md | 20 ++++++++++++++++++++ package.json | 2 +- src-tauri/Cargo.lock | 2 +- src-tauri/Cargo.toml | 2 +- src-tauri/tauri.conf.json | 2 +- 7 files changed, 24 insertions(+), 26 deletions(-) delete mode 100644 .changeset/history-knows-its-collection.md delete mode 100644 .changeset/select-by-section-too.md diff --git a/.changeset/history-knows-its-collection.md b/.changeset/history-knows-its-collection.md deleted file mode 100644 index d1f2cb0..0000000 --- a/.changeset/history-knows-its-collection.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -'fiber': patch ---- - -Keep each collection's response history to itself. - -Response history was bucketed by request id alone. A loaded endpoint's id is `METHOD /path` and carries no section, so two collections describing the same API — staging and production — shared one list: opening either showed whichever had been sent last, and clearing one deleted both. - -The database has stored `section_id` since the column was added; it was simply never handed back. It is now, so the window can tell the two apart, and clearing is scoped to the collection you cleared. - -Entries recorded before this still show for either collection rather than disappearing, since nothing knows which one they came from. A scoped clear takes them too — they are the same request's older entries, and leaving them behind would look like the clear half-worked. diff --git a/.changeset/select-by-section-too.md b/.changeset/select-by-section-too.md deleted file mode 100644 index ae01181..0000000 --- a/.changeset/select-by-section-too.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -'fiber': patch ---- - -Select an endpoint in the collection you clicked it in. - -Two collections describing the same API — staging and production — give every loaded endpoint the same id, because a loaded id is `METHOD /path` and deliberately carries no section: that is the identity a saved body and a refresh have to agree on, so a re-run re-attaches instead of orphaning. - -Selection was keyed on that id alone. So both rows highlighted at once, the pane always resolved to whichever collection sorted first, and the second one could not be opened at all — clicking it set an id the store already held, so nothing changed. The selection now carries the section as well. - -Note that response history is still bucketed by request id, so the same endpoint in two collections shares one history. That is the same root cause and is not fixed here. diff --git a/CHANGELOG.md b/CHANGELOG.md index 4ed8d2d..1d58a84 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,25 @@ # fiber +## 0.14.8 + +### Patch Changes + +- [#87](https://github.com/MathiasWP/fiber/pull/87) [`a703582`](https://github.com/MathiasWP/fiber/commit/a7035828c254598b31d5d0022fc36a4b3d2f5afc) Thanks [@MathiasWP](https://github.com/MathiasWP)! - Keep each collection's response history to itself. + + Response history was bucketed by request id alone. A loaded endpoint's id is `METHOD /path` and carries no section, so two collections describing the same API — staging and production — shared one list: opening either showed whichever had been sent last, and clearing one deleted both. + + The database has stored `section_id` since the column was added; it was simply never handed back. It is now, so the window can tell the two apart, and clearing is scoped to the collection you cleared. + + Entries recorded before this still show for either collection rather than disappearing, since nothing knows which one they came from. A scoped clear takes them too — they are the same request's older entries, and leaving them behind would look like the clear half-worked. + +- [#85](https://github.com/MathiasWP/fiber/pull/85) [`ba28ebb`](https://github.com/MathiasWP/fiber/commit/ba28ebbc3e43dd1059b53f97c3e5c0727b2657fd) Thanks [@MathiasWP](https://github.com/MathiasWP)! - Select an endpoint in the collection you clicked it in. + + Two collections describing the same API — staging and production — give every loaded endpoint the same id, because a loaded id is `METHOD /path` and deliberately carries no section: that is the identity a saved body and a refresh have to agree on, so a re-run re-attaches instead of orphaning. + + Selection was keyed on that id alone. So both rows highlighted at once, the pane always resolved to whichever collection sorted first, and the second one could not be opened at all — clicking it set an id the store already held, so nothing changed. The selection now carries the section as well. + + Note that response history is still bucketed by request id, so the same endpoint in two collections shares one history. That is the same root cause and is not fixed here. + ## 0.14.7 ### Patch Changes diff --git a/package.json b/package.json index f420384..dc8e2d2 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "name": "fiber", "private": true, - "version": "0.14.7", + "version": "0.14.8", "type": "module", "packageManager": "pnpm@11.22.0", "engines": { diff --git a/src-tauri/Cargo.lock b/src-tauri/Cargo.lock index 0583385..6aa7bb8 100644 --- a/src-tauri/Cargo.lock +++ b/src-tauri/Cargo.lock @@ -1285,7 +1285,7 @@ dependencies = [ [[package]] name = "fiber" -version = "0.14.7" +version = "0.14.8" dependencies = [ "base64 0.23.1", "dirs", diff --git a/src-tauri/Cargo.toml b/src-tauri/Cargo.toml index 2479e8b..1138734 100644 --- a/src-tauri/Cargo.toml +++ b/src-tauri/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "fiber" -version = "0.14.7" +version = "0.14.8" 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 52dd946..c3cfe14 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.14.7", + "version": "0.14.8", "identifier": "dev.fiber.app", "build": { "frontendDist": "../build",