10.6.0
Namespaces produced by a tool are now marked, and hand edits to them are reported in review.
-
Generated namespaces (#1359). A
namespaceConfigentry can carry anoriginmarker naming the tool that produced it. Unlike a read-only namespace, a generated one is meant to be refined by hand, so the reusable workflow annotates changes to it instead of failing them. New:RuneOriginConfiguration,RuneNamespaceConfiguration.getOrigin(), and a generated namespaces documentation page. -
One namespace-pattern matcher (#1360).
RuneNamespacePatternis now the single interpretation of a namespace pattern, shared by the generators filter and the CI checkers.Behaviour change to the read-only namespace check. Only a terminal
.*is a wildcard: it covers the namespace itself and its subnamespaces, matched by whole segments. Other glob syntax —foo*,a?c,a[bc]— is now read as an exact namespace and matches nothing, which the existing stale-pattern guard reports. No repository calling the workflow uses a wildcard read-only pattern today, but all of them pick this up, since they track@main.