Skip to content

Fix flake.lock bump host eval failures (MCP command type + Jellyfin 10.11.11 hash)#76

Draft
BCNelson with Copilot wants to merge 1 commit into
mainfrom
copilot/copilotflake-lock-bump-28019194966
Draft

Fix flake.lock bump host eval failures (MCP command type + Jellyfin 10.11.11 hash)#76
BCNelson with Copilot wants to merge 1 commit into
mainfrom
copilot/copilotflake-lock-bump-28019194966

Conversation

Copilot AI commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

The scheduled flake.lock bump failed in check-hosts after dependency updates changed evaluation behavior for two hosts. This PR applies the smallest scoped config updates needed to restore host evaluation on the lock-bump branch.

  • Home Manager MCP config typing (redo-2)

    • programs.mcp.servers.aws-support-mcp-server.command now passes a string path, matching the module type (null or string) expected by Home Manager.
  • nixarr Jellyfin OpenAPI hash compatibility (romeo-2)

    • Extended the temporary python-deps.nix patch injection to include Jellyfin 10.11.11, resolving the missing-version hash lookup introduced by the lock update.
  • Targeted diff only

    • Changes are limited to:
      • home-manager/bcnelson/_mixins/mcp/aws/support.nix
      • nixos/romeo/nixarr.nix
# before
command = awsSupportLauncher;

# after
command = "${awsSupportLauncher}";
"10.11.10" = "sha256-3FfqhqQfuQdM/02NyhAWDW7H6OaTynWtaUBoSIxk4AQ=";
"10.11.11" = "sha256-4p/DaeyuVGdsrrUMu8AGtcTulZkGwA8eAvb4PbnCJ/s=";

Copilot AI changed the title [WIP] Fix failed flake.lock bump workflow Fix flake.lock bump host eval failures (MCP command type + Jellyfin 10.11.11 hash) Jun 23, 2026
Copilot AI requested a review from BCNelson June 23, 2026 10:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants