Guchho 1.0.6
Plugins scoped per configuration element, and documentation clean-up.
#Released 2026-10-14.
Plugins
#When the config file's root is an array of configurations, each element's
plugins now run for that element's build and no other. Previously every
element's plugins were merged into one list for the whole run.
- Each build receives one group, positionally aligned with the config root, so a plugin named by two elements is reached as two separate instances. That is the case a single flat list cannot express - a host with a plugin per output names the same plugin on each element and needs each build to reach its own.
- An element that names no plugins contributes an empty group, and its build runs with none; a plugin from another element does not leak onto it.
- A single-configuration root is one group and behaves exactly as before, and a
host that passes one flat
pluginslist still applies it to every build.
From C++ the same behaviour is available through the new
RunWithPluginGroups, alongside the existing RunWithPlugins. The service
carries the groups and tells each callback which build is calling, so a name
that appears in two elements resolves to the right instance.
Documentation
#- Wording clean-up across the documentation tree, replacing em dashes with hyphens throughout.
Upgrading
#Nothing here is breaking. A config file whose root is a single object, and a
plugins list passed in code, both behave as before.
npm install -g guchho@1.0.6
Full comparison:
v1.0.5…v1.0.6.