novox/mesh-catalog
9
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Remove resolv-conf (hq ADR 0223 part 2, step 2 of 2) #77

Merged
mesh-admin merged 1 commits from retire-resolv-conf into main 2026-10-05 22:08:02 +00:00
Conversation 1 Commits 1 Files Changed 2
-19
mesh-admin commented 2026-10-05 21:45:03 +00:00
Contributor
Copy Link
Copy Source

Stacked on resolv-conf-to-uplink; retarget to main once that merges.

Merge only after every machine has applied step 1 (resolv-conf.fact-resolvers forgotten, <uplink>.fact-resolvers recorded), unassign <node> resolv-conf on all four, a push, and module forget resolv-conf. Together with mesh-controller retire-resolv-conf.

Stacked on `resolv-conf-to-uplink`; retarget to main once that merges. **Merge only after** every machine has applied step 1 (resolv-conf.fact-resolvers forgotten, `<uplink>.fact-resolvers` recorded), `unassign <node> resolv-conf` on all four, a push, and `module forget resolv-conf`. Together with mesh-controller `retire-resolv-conf`.
mesh-admin changed target branch from resolv-conf-to-uplink to main 2026-10-05 22:07:39 +00:00
mesh-admin added 1 commit 2026-10-05 22:07:39 +00:00
Remove resolv-conf now that the uplink's holder writes resolv.conf (hq ADR 0223) dd124966ad 
Merge only once resolv-conf is unassigned on every machine and forgotten.
mesh-admin merged commit ed6384feb0 into main 2026-10-05 22:08:02 +00:00
mesh-admin deleted branch retire-resolv-conf 2026-10-05 22:08:02 +00:00
mesh-admin commented 2026-10-06 23:09:20 +00:00
Author
Contributor
Copy Link
Copy Source

Delivery novox/mesh-catalog@ed6384feb0b0 — held since 2026-10-06T23:05:28Z

Held for a person: merged without a passing check: only a person decides that it goes on — mesh-delivery.release with why lets it go on.

Delivery plan — builds new: modules/resolv-conf, sent nowhere; no bus step

Transitions

  • 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-catalog#77 merged; its head was not heard by this owner, so it is made from the forge's word
  • 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@ed6384feb0b0` — **held** since 2026-10-06T23:05:28Z Held for a person: merged without a passing check: only a person decides that it goes on — `mesh-delivery.release` with why lets it go on. **Delivery plan** — builds new: modules/resolv-conf, sent nowhere; no bus step **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-catalog#77 merged; its head was not heard by this owner, so it is made from the forge's word - 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
mesh/ready
Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#77