Files
deepseek-harness/vendor/group
imccyu 97eb14a007 build(release): make the release set publishable under the private scope
Every package under packages/, apps/, and vendor/ drops "private": true and
declares publishConfig.access "restricted": the repository now states which
packages it publishes instead of deciding it at publish time. Each one also
declares its repository and directory, which is how a consumer of a private
package reaches its source.

The Landlock packages move to restricted with them. They have never been
published, so nothing anonymous depends on them today, and the whole
@deepseek-ai scope stays private.

The workspace constraint that required every package to be private now applies
to non-members only, and asserts the publishable trio on each release member.
2026-08-11 00:09:31 +08:00
..

@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.