mirror of https://github.com/deepseek-ai/deepseek-harness synced 2026-08-15 21:04:50 +00:00

Files

imccyu a213befd0f build(release): publish the vendored framework and the native packages publicly

The three release sequences shipped with publishConfig.access: restricted, so
nothing in the @deepseek-ai scope was installable from outside the organization.

A restricted dependency is what actually blocks a public consumer: every harness
package declares the vendored framework as a peerDependency, and
dsh-sandbox-local declares the Landlock entry as a dependency. Those two
sequences therefore go public first — the nine vendor/* packages and the three
native/landlock-run packages — while the dsh family stays restricted until its
own sequence is opened deliberately. No public package requires a restricted one
in this arrangement.

Access is now per sequence, so no publish path can pass --access: one flag
cannot express two levels and would override the manifest that owns the fact.
publish.ts stops passing it, matching the native workflow, and
check-workspace-constraints holds each manifest to its own sequence's level,
which is what stops the scope from drifting one package at a time.

Harness consumers reference the Landlock entry as workspace:^ instead of
workspace:*, so a published harness package accepts the entry's patch and minor
releases. The entry keeps workspace:* for its platform packages, where the
binary must match the entry version exactly.

Two rationales that named a private registry no longer describe the vendored
sequence; they now state the durable reason, which is that the verification must
not depend on the registry already carrying matching versions.

2026-08-13 14:05:48 +08:00

src

Merge remote-tracking branch 'origin/master' into feat/loader-entry-disabled-interpolation

2026-08-11 18:43:40 +08:00

LICENSE

Vendor Cordis framework packages as source

2026-06-11 10:53:32 +08:00

package.json

build(release): publish the vendored framework and the native packages publicly

2026-08-13 14:05:48 +08:00

README.md

Vendor Cordis framework packages as source

2026-06-11 10:53:32 +08:00

tsconfig.json

refactor: rename build typings dir to types

2026-06-20 00:26:02 +08:00

tsdown.config.ts

refactor: remove repository plugin path

2026-08-10 21:32:13 +08:00

README.md

@cordisjs/plugin-loader

Runtime plugin loader for Cordis. The loader owns an EntryTree, imports plugin modules by name, applies their config, and keeps the running plugin graph in sync with entry updates.

Usage

import { Context } from 'cordis'
import Loader from '@cordisjs/plugin-loader'

const root = new Context()
await root.plugin(Loader, { baseUrl: import.meta.url })

const id = await root.loader.create({
  name: './plugins/example',
  config: { enabled: true },
})

await root.loader.await()
root.loader.update(id, { config: { enabled: false } })

Entry Options

Field	Description
`id`	Stable id for resolving, updating, and removing the entry.
`name`	Module specifier imported by the loader.
`config`	Config passed to the plugin.
`group`	Marks the entry as a group whose `config` is a child entry list.
`disabled`	Stops the entry and prevents it from starting.
`inject`	Adds required services or intercept config for this entry.

API

API	Description
`loader.create(options, parent?, position?)`	Add and start an entry.
`loader.update(id, options, parent?, position?)`	Update, move, and restart an entry.
`loader.remove(id)`	Stop and delete an entry.
`loader.resolve(id)`	Resolve an entry by id, including nested `a:b` ids.
`loader.resolveGroup(id)`	Resolve the root group or a nested group.
`loader.await()`	Wait for pending entry imports and fiber reloads.
`loader.locate(fiber?)`	Return the loader entry id that owns a fiber.

For file-backed trees, use @cordisjs/plugin-include.