From abf7c9e40ba2685a4cd722bf362b9caf3b057247 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Mon, 7 Sep 2026 06:39:48 +0000
Subject: [PATCH] Version Packages

---
 .changeset/one-prompt-not-a-thousand.md | 27 ------------------------
 CHANGELOG.md                            | 28 +++++++++++++++++++++++++
 package.json                            |  2 +-
 src-tauri/Cargo.lock                    |  2 +-
 src-tauri/Cargo.toml                    |  2 +-
 src-tauri/tauri.conf.json               |  2 +-
 6 files changed, 32 insertions(+), 31 deletions(-)
 delete mode 100644 .changeset/one-prompt-not-a-thousand.md

diff --git a/.changeset/one-prompt-not-a-thousand.md b/.changeset/one-prompt-not-a-thousand.md
deleted file mode 100644
index 958f335..0000000
--- a/.changeset/one-prompt-not-a-thousand.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-"fiber": patch
----
-
-A collection the API is rejecting no longer re-runs its loader every time you
-click back into the window, and editing one no longer reaches for the keychain.
-
-Between them those two made the app unusable after an update. Fiber is signed
-ad-hoc, so a new build is a new identity and every keychain item's access list
-names the old one: for one launch after every update, each credential read is a
-macOS authorization dialog. That is the intended cost, and it should be one
-dialog per credential.
-
-It was not, because a failed loader run writes no cache. `loadedAt` never moved,
-so the collection stayed stale and the focus trigger re-ran it — and the
-authorization dialog is itself a focus event, handing the window back the moment
-it is dismissed. Allow, refocus, re-run, prompt again, for as long as the
-credential is being refused. A failure now counts as an attempt, so the TTL
-means the same thing for both outcomes: don't ask this API again for another
-`ttlSeconds`. Refresh and Sign in again are unaffected — those are you asking.
-
-The second one arrived with the credentials file in 0.15.0. Saving a section
-reconciled that file, and reconciling it means unsealing it, and unsealing it
-means reading the sealing key from the keychain. Fiber saves a section on any
-edit, so renaming a request could raise a password prompt. It is now reconciled
-only when sharing itself moves — the switch, or which credential the collection
-uses — which is what it was always for.
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 1f5229c..717d874 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,33 @@
 # fiber
 
+## 0.16.1
+
+### Patch Changes
+
+- [#97](https://github.com/MathiasWP/fiber/pull/97) [`a2b9a8c`](https://github.com/MathiasWP/fiber/commit/a2b9a8c7964d03865f51883b1595a772d274145a) Thanks [@AndersRobstad](https://github.com/AndersRobstad)! - A collection the API is rejecting no longer re-runs its loader every time you
+  click back into the window, and editing one no longer reaches for the keychain.
+  
+  Between them those two made the app unusable after an update. Fiber is signed
+  ad-hoc, so a new build is a new identity and every keychain item's access list
+  names the old one: for one launch after every update, each credential read is a
+  macOS authorization dialog. That is the intended cost, and it should be one
+  dialog per credential.
+  
+  It was not, because a failed loader run writes no cache. `loadedAt` never moved,
+  so the collection stayed stale and the focus trigger re-ran it — and the
+  authorization dialog is itself a focus event, handing the window back the moment
+  it is dismissed. Allow, refocus, re-run, prompt again, for as long as the
+  credential is being refused. A failure now counts as an attempt, so the TTL
+  means the same thing for both outcomes: don't ask this API again for another
+  `ttlSeconds`. Refresh and Sign in again are unaffected — those are you asking.
+  
+  The second one arrived with the credentials file in 0.15.0. Saving a section
+  reconciled that file, and reconciling it means unsealing it, and unsealing it
+  means reading the sealing key from the keychain. Fiber saves a section on any
+  edit, so renaming a request could raise a password prompt. It is now reconciled
+  only when sharing itself moves — the switch, or which credential the collection
+  uses — which is what it was always for.
+
 ## 0.16.0
 
 ### Minor Changes
diff --git a/package.json b/package.json
index 9ce90a7..dbd5058 100644
--- a/package.json
+++ b/package.json
@@ -1,7 +1,7 @@
 {
 	"name": "fiber",
 	"private": true,
-	"version": "0.16.0",
+	"version": "0.16.1",
 	"type": "module",
 	"packageManager": "pnpm@11.22.0",
 	"engines": {
diff --git a/src-tauri/Cargo.lock b/src-tauri/Cargo.lock
index 2698ae8..c34b3ae 100644
--- a/src-tauri/Cargo.lock
+++ b/src-tauri/Cargo.lock
@@ -1354,7 +1354,7 @@ dependencies = [
 
 [[package]]
 name = "fiber"
-version = "0.16.0"
+version = "0.16.1"
 dependencies = [
  "base64 0.23.1",
  "chacha20poly1305",
diff --git a/src-tauri/Cargo.toml b/src-tauri/Cargo.toml
index 0b6eb6f..f070485 100644
--- a/src-tauri/Cargo.toml
+++ b/src-tauri/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "fiber"
-version = "0.16.0"
+version = "0.16.1"
 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 feabfef..1e7f44e 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.0",
+  "version": "0.16.1",
   "identifier": "dev.fiber.app",
   "build": {
     "frontendDist": "../build",