v0.263.2: the undo keeps the probe of the pinned version (R-637)
gates / gates (push) Successful in 25s

Found live on 9202 (romm): .felhom.yml flows into the stack dir on every
catalog sync, so "the old .felhom.yml" saved at update time was already the
new one, and the serving old version was judged with the new probe.

New record applied-meta/.felhom.yml, written whenever a version is pinned
(deploy, adoption, pin advance) and put back by the undo, like
applied-compose.yml. The fixture now places the new file at sync time.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
adminandClaude Opus 5.5 committed 2026-09-23 11:53:53 +02:00
1 parent 5d38573a1a
commit 2cd66663f3
7 files changed
+197 -20

No files matched your search

+3
View File
@@ -281,6 +281,7 @@ func (m *Manager) AdoptPins() int {
m.logger.Printf("[ERROR] [stacks] pin adoption: %s: %v", s.Name, err)
continue
}
m.storeAppliedMetaFrom(s.Name, stackDir, filepath.Join(stackDir, ".felhom.yml")) // adopted only when running == template
pinned++
}
@@ -359,6 +360,8 @@ func (m *Manager) advancePinToCatalog(name, stackDir string) error {
}
m.mu.Unlock()
// v0.263.2: the new version's own .felhom.yml becomes the pinned version's record.
m.storeAppliedMetaFrom(name, stackDir, m.CatalogTemplatePath(name, ".felhom.yml"))
m.logger.Printf("[INFO] [stacks] update %s: pin advanced to the catalog's current definition (%s)", name, summarisePin(pin))
return nil
}