Repository navigation
fix(mcp): avoid runtime flake resolution - #51
Merged
Merged
Conversation
Realize the pinned mcp-nixos closure with Home Manager so network cache retries cannot consume the MCP startup budget. Keep the shared V1-compatible configuration that V2 normalizes.
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.
Outcome
Launch the pinned mcp-nixos 2.4.3 executable from the realized Home Manager closure instead of resolving a flake during MCP initialization. Preserve the shared V1-compatible configuration consumed by V2.
Validation
just check-fullpasses after reconciliation with current main.Rollout
Publish and verify FlakeHub artifact first. Consumer pins it before Endeavour-only Home Manager activation; separate field-preserving V2 snapshot refresh retains unrelated settings.
Recovery
Revert this change and publish a replacement artifact; consumer rollback retains its narrow V2 refresh activation and restores prior input pin.