Draft
Fix flake.lock bump host-check regressions (redo-2 MCP type + romeo-2 Jellyfin hash)#70
Conversation
Copilot
AI
changed the title
[WIP] Fix failed flake.lock bump
Fix flake.lock bump host-check regressions (redo-2 MCP type + romeo-2 Jellyfin hash)
Jun 20, 2026
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
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.
The scheduled flake.lock bump updated inputs to revisions that broke
check-hostson two hosts. This PR keeps the lock bump and applies two narrow compatibility fixes so host evaluation can proceed again.Home Manager MCP command typing (
redo-2)programs.mcp.servers.aws-support-mcp-server.commandwas set to a derivation, but current Home Manager expectsnull | string.nixarr Jellyfin OpenAPI hash patch (
romeo-2)nixos/romeo/nixarr.nixpatch only covered Jellyfin OpenAPI hashes through10.11.10.10.11.11hash entry to match the bumped dependency set.