Version Packages - #93
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
fiber@0.15.0
Minor Changes
#92
2414209Thanks @MathiasWP! - Signing in again now reaches a running containerised MCP server.Under ToolHive the server took its credentials from
FIBER_SECRETS, read onceat startup, so a container held whatever was true when it began: you signed in,
the keychain got the new token, and the server went on presenting the expired
one until someone re-exported the secrets and replaced the workload.
Credentials can now travel through the collections directory the container
already mounts. The app rewrites that file whenever a credential changes, the
server re-reads it, and the 401 retry that was already there picks the new value
up — no re-export, no restart.
The file is sealed with XChaCha20-Poly1305 and the key stays out of the mount:
in the keychain on the app's side, in ToolHive's encrypted store on the
container's. Its existence is the opt-in, so a desktop-only install never has
credentials on disk. New:
fiber mcp file-keyandfiber mcp export-secrets --to <path>;scripts/toolhive.shwires both up for you.Bearer collections needed a second fix to benefit: a static token cannot be
refreshed by replaying a request, so a 401 never dropped it, and a zero-TTL
cache entry has nothing else to expire it — a container would have presented
the token it started with for the life of the workload. A rejected credential
is now dropped from the cache whenever it came from a source that can change
underneath the process, so the next call reads the new one. The desktop app is
unaffected: it has no such source, and the same line there would have cost a
keychain prompt per 401.