8 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	9cb177cae6	Pin mesh-sdk 6e4a301 in the modules the release changes, and keep the others on their pins (issue 774)	2026-10-30 00:23:45 +01:00
jschoubben	475ffdcb33	gitea waits and keeps serving while its keys are unread; pin mesh-sdk 007b6fd ... After a restart the forge-account provider returned a plain error, which the helper writes as failed with its values cleared, so every consumer lost its forge entry until the keys loaded. provider.ErrNotReady keeps the entry serving, in waits (issue 1954).	2026-10-30 00:04:14 +01:00
jschoubben	cb7a5c9939	mesh-provisioner composes through fromruntime's reader; pin mesh-sdk fa5a6ae across A3's modules ... The SDK now reads a module's `reads` through the runtime, so busread.go's own copy goes, and the manifest is held to frombus.StatesReads (issue 1954).	2026-10-30 00:02:38 +01:00
jschoubben	451d790edd	Judge each provider by what its manifest declares and fill what a provision depends on, so a templated pair provider is provided only after its credential (issue 1954) ... A provider declaring bound is judged by its entries, any other by its own have, and only once every provision it depends on, its secret-<provision> first, is provided. The credential is the vault's own provision. One integration test runs the holder on a real bus over mesh-sdk's in-memory mesh: a want composes the key, the outcomes provide it, leaving the node asks. Pins mesh-sdk 6b8c694.	2026-10-29 22:49:26 +01:00
jschoubben	6bee0b6789	Never set a provision provided without its provider's outcome, read from the entry's state and why, and pin mesh-sdk 692dbf9 (issue 1954) ... A provider that writes no outcome leaves its keys asked (ADR 0570 clause 3), so a provider that fails is never hidden.	2026-10-29 22:43:16 +01:00
jschoubben	0a2334e2cd	Compose every provision and plan in mesh-provisioner from the bus on change events, its state from the providers' outcomes, and ask before retiring (issue 1954) ... The seat holds provisions and plans alone (ADR 0570 §1-§3, §5): a node is composed at its wanted builds and its newest, so a key ahead of its want is never retiring; a key no build needs is retiring with one ask, and the warrant goes into the key for its provider. The registry's placement kinds name plans; needs is emptied at start. Pins mesh-sdk 66ff33d.	2026-10-29 22:41:29 +01:00
jschoubben	92c5e1d9ae	Pin mesh-provisioner, mesh-vault and rofi to a commit of mesh-sdk main, since the pinned one is on no branch and no fetch can resolve it (issue 1659)	2026-10-21 13:14:57 +02:00
mesh-tools	0260ae92f6	Feature 57 (config and provisioning): release the catalogue, the reviewed release branch merged with main, on top of main	2026-10-16 09:42:45 +00:00