imccyu
2c85c484d3
1504 hand-written ranges pointing at workspace members become workspace:^, so pnpm pack substitutes each member's real version at publication: sibling peerDependencies follow the family version instead of being pinned at ^0.0.1, and a reference to a vendored package follows that package's own line. Without this, publishing 0.0.2 ships peer ranges naming a version that does not exist, and 0.0.1-rc.1 does not satisfy ^0.0.1 either. It also retires ranges that had gone stale against the workspace: ^4.0.0-rc.6 for a 4.0.0-rc.7 checkout, ^3.17.0 for schemastery 3.18.0. workspace:* stays where an exact published version is the point, which is how the Landlock entry pins its platform packages. A workspace constraint now requires the protocol, so a new package cannot reintroduce a hand-written range. The same constraint caught packages/boot/cmdline arriving on master without the publishable trio, which this change completes.
@cordisjs/plugin-group
Loader group plugin for nesting Cordis entries.
Usage
- id: tools
name: '@cordisjs/plugin-group'
group: true
config:
- id: logger
name: '@cordisjs/plugin-logger-console'
Groups are always considered enabled themselves, but disabling a group entry
prevents its child entries from running. Nested entry ids use : separators,
for example tools:logger.
The package re-exports the Group implementation from
@cordisjs/plugin-loader as its default plugin.