build(flake): let mcphub keep its own nixpkgs #61

Merged
marti merged 1 commit from feature/mcphub-own-nixpkgs into main 2026-11-12 02:30:13 +01:00
Owner

Summary

This is the mcphub follow-up to #60. mcphub's module used to build its images with the host's packages, so #60's fix could not apply to it. Since marti/mcphub#54, the module deploys the flake's own images, which mcphub's CI builds. With the follows dropped, cum-tools asks for exactly those images and fetches them from cum-ci's cache.

 flake.nix
   mcphub = { url = ...;
-    inputs.nixpkgs.follows = "nixpkgs";
     inputs.trail-code.inputs.nixpkgs.follows = "nixpkgs"; };

 flake.lock
-  mcphub 5b1de63   (nixpkgs: follows ours)
+  mcphub a724e93   (nixpkgs: 1d06008, mcphub's own pin)

Evidence

The images cum-tools deploys, compared with mcphub's checks.x86_64-linux.* at a724e93:

before after mcphub CI
mcphub (and egress) 0yfqakyw…-mcphub.tar.gz qysdsk98…-mcphub.tar.gz qysdsk98…
runner xqny9zds…-mcphub-runner.tar.gz f38qn1x2…-mcphub-runner.tar.gz f38qn1x2…
  • nix flake check --no-build: all checks pass.
  • trail check: no conflicts.

Merge Danger

Door: two-way

Blast Radius: cum-tools

The mcphub, egress and runner containers restart onto newly tagged images. Their contents differ only in being built with mcphub's own nixpkgs. Migrations run first, as on every image change. If cum-ci's cache has already dropped the images, cum-tools builds them itself, as it does today.

🤖 Generated with Claude Code

## Summary This is the mcphub follow-up to #60. mcphub's module used to build its images with the host's packages, so #60's fix could not apply to it. Since marti/mcphub#54, the module deploys the flake's own images, which mcphub's CI builds. With the follows dropped, cum-tools asks for exactly those images and fetches them from cum-ci's cache. ```diff flake.nix mcphub = { url = ...; - inputs.nixpkgs.follows = "nixpkgs"; inputs.trail-code.inputs.nixpkgs.follows = "nixpkgs"; }; flake.lock - mcphub 5b1de63 (nixpkgs: follows ours) + mcphub a724e93 (nixpkgs: 1d06008, mcphub's own pin) ``` ## Evidence The images cum-tools deploys, compared with mcphub's `checks.x86_64-linux.*` at `a724e93`: | | before | after | mcphub CI | |---|---|---|---| | mcphub (and egress) | `0yfqakyw…-mcphub.tar.gz` | `qysdsk98…-mcphub.tar.gz` | `qysdsk98…` | | runner | `xqny9zds…-mcphub-runner.tar.gz` | `f38qn1x2…-mcphub-runner.tar.gz` | `f38qn1x2…` | - `nix flake check --no-build`: all checks pass. - `trail check`: no conflicts. ## Merge Danger **Door:** two-way **Blast Radius:** cum-tools The mcphub, egress and runner containers restart onto newly tagged images. Their contents differ only in being built with mcphub's own nixpkgs. Migrations run first, as on every image change. If cum-ci's cache has already dropped the images, cum-tools builds them itself, as it does today. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
mcphub's NixOS module now deploys the flake's own images, which its CI
builds (marti/mcphub#54). With nixpkgs no longer following ours,
cum-tools deploys exactly those derivations and fetches them from
cum-ci's cache instead of building them: qysdsk98...-mcphub.tar.gz and
f38qn1x2...-mcphub-runner.tar.gz, the same as mcphub's
checks.x86_64-linux.image and .runner-image at a724e93.

Bumps mcphub 5b1de63 -> a724e93, whose only change is that.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
marti merged commit 7a3e80264e into main 2026-11-12 02:30:13 +01:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cumsek/nix!61
No description provided.