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

refactor(cmdline): trim the command-line seams to existing interfaces

2026-08-11 18:00:15 +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

README.md

@cordisjs/plugin-include

File-backed loader tree for Cordis. The include plugin reads a YAML or JSON file, turns it into loader entries, and writes updates back when the file is writable.

Usage

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

const root = new Context()
await root.plugin(Loader, { baseUrl: import.meta.url })
await root.plugin(Include, {
  path: './cordis.yml',
  initial: [],
  enableLogs: true,
})

Example cordis.yml:

- id: timer
  name: '@cordisjs/plugin-timer'
- id: app
  name: ./plugins/app
  config:
    message: hello

Config

Field	Description
`path`	YAML or JSON file path resolved from `ctx.baseUrl`.
`initial`	Entry list written when the file is missing.
`patches`	Runtime patches applied after reading the file.
`enableLogs`	Enables loader apply, reload, and unload logs.

Patches can insert entries or override fields on entries with a matching id.