Skip to content

Unblock flake.lock bump host checks for redo-2 and romeo-2#72

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

Unblock flake.lock bump host checks for redo-2 and romeo-2#72
BCNelson with Copilot wants to merge 1 commit into
mainfrom
copilot/copilotflake-lock-bump-27901218356

Conversation

Copilot AI commented Jun 21, 2026

Copy link
Copy Markdown
Contributor

The scheduled flake.lock bump failed in check-hosts due to two independent evaluation breakages introduced by input drift: a Home Manager option type mismatch on redo-2, and a missing Jellyfin OpenAPI hash mapping on romeo-2. This PR applies the narrowest config-level fixes to restore host evaluation on the lock-bump branch.

  • Home Manager MCP server command type (redo-2)

    • Updated aws-support-mcp-server.command to a string path instead of a derivation value to satisfy the current option type contract (null or string).
  • nixarr Jellyfin hash patch extension (romeo-2)

    • Extended the existing temporary python-deps.nix substitution in nixos/romeo/nixarr.nix to include Jellyfin 10.11.11 hash mapping.
    • Kept the fix scoped to the existing local patch mechanism (no broader nixarr refactor).
  • Representative change

    programs.mcp.servers.aws-support-mcp-server = {
      command = "${awsSupportLauncher}";
      # ...
    };
    
    # in nixos/romeo/nixarr.nix substitution payload
    "10.11.11" = "sha256-4p/DaeyuVGdsrrUMu8AGtcTulZkGwA8eAvb4PbnCJ/s=";

Copilot AI changed the title [WIP] Fix failed flake.lock bump Unblock flake.lock bump host checks for redo-2 and romeo-2 Jun 21, 2026
Copilot AI requested a review from BCNelson June 21, 2026 10:26
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