Config and chat adapter releases shipped against stale cores, prompting a new CI guard
The estate's Go modules are organised into families, each with a core module and adapter modules that depend on it, so releases must follow a set order. A recent batch of twenty-three config adapters was released before the core update they needed, leading to thirty-nine follow-up releases to correct it. A similar problem occurred with chat adapters soon after a core release. The release tool colophon has no pre-release hook, so the fix was built as a separate CI component, go-core-currency, that checks whether adapters depend on the latest core. Module membership is read from each go.mod rather than a public project list, and the guard starts as a non-blocking warning before becoming enforceable.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in