bowenliang123
9acbf7eb45
The supported range is now two baselines - dsh-v0.1.5-rc.1 (session
format V3) and dsh-v0.1.7-rc.2 (V4) - enforced by the runtime gate at
BASELINE_DSH_VERSION = 0.1.5-rc.1; below it the fallback units and the
upgrade modal take over (0.1.2/0.1.3 hosts were previously served by the
real folds).
The pre-V3 log shapes are dead code on every supported harness: the
running harness migrates historical logs on every read path (or refuses
the session wholesale), and 0.1.5-rc.1 rejects a request/header carrying
header.system outright. The fold therefore drops the V0/V2-only paths -
the header.system envelope system prompt, assistant/chunk floods,
{start, end} replacement endpoints, tool/code-dispatch - and the state
fields only they wrote (systemsFromHeader, the stepStart decode
accumulators). stateVersion stays 20: no supported log folds
differently, and pre-V3-era cached rows are discarded by the projection
cache's identity gate (and the strict stepStart sub-schema) instead of
served. The headers unit folds metadata-only epochs (envelope
systemTokens write dropped; the v1 cached-row read-compat and its pinned
stateVersion 1 stay); replaceRangeOf speaks startSeq/endSeq only; the
browser's epoch fetch maps request/header to tools and system/message to
the prompt text.
tests/baselines.ts re-fits to the two entries (the right Sidebar seam is
required on both), the compat matrix drives both tags' REAL sources
(canonical logs re-shaped to V3, the hostile probe renumbered past them),
and the version fixtures pin the new floor. Manifest: dshReleases
{0.1.5-rc.1, 0.1.7-rc.2}, dsh peers >=0.1.5-rc.1 (satisfies the 0.1.7
admission check under includePrerelease), devDeps pinned to the
0.1.5-rc.1 surface plus the ui-primitives runtime closure the client
lane inlines (test-only), and the release workflow fetches the two tags.
docs/compatibility.md is rewritten around the two-line matrix; README,
AGENTS.md and the issue template follow.
Also riding this move, from the audit pass: the fold re-proves an inject
source's form before it books the event record (the harness validates
`kind` but not `form` - a hostile one previously failed the strict
wire/state schemas on every delivery, the #44 freeze class), the headers
unit guards a data-less envelope (it has no try/catch of its own), the
schemastery schema annotations drop the explicit z<T> wrappers the 3.18.4
Mode generics reject, and the version-history note records why
stateVersion is deliberately not bumped.
85 lines
2.9 KiB
YAML
85 lines
2.9 KiB
YAML
name: Publish to npm
|
|
|
|
# Fires on a release tag (v*) push. Publishing uses npm Trusted Publishing
|
|
# (OIDC), so no long-lived token is needed — the npm-side trusted publisher
|
|
# must be configured with this exact workflow filename.
|
|
on:
|
|
push:
|
|
tags:
|
|
- 'v*'
|
|
|
|
permissions:
|
|
id-token: write # Required for OIDC
|
|
contents: read
|
|
|
|
jobs:
|
|
publish:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: actions/checkout@v7
|
|
|
|
- name: Check the DeeSeek Harness plugin
|
|
# `next` = the newest published generation (0.1.7-rc.2), whose npm
|
|
# dependency closure is complete. The 0.1.5-rc `latest` line is
|
|
# transitively broken on npm right now: web-app 0.1.5-rc.3 was
|
|
# published without the dsh-client-ui-sidebar-documentpreview rc.3 it
|
|
# requests, and every ^0.1.5-rc range resolves to it. Revisit when
|
|
# upstream republishes a complete stable closure.
|
|
uses: bowenliang123/dsh-plugin-checker@v1
|
|
with:
|
|
dshVersion: next
|
|
|
|
# Reads the pinned pnpm version from `packageManager` in package.json.
|
|
- uses: pnpm/action-setup@v6
|
|
with:
|
|
version: latest
|
|
|
|
- uses: actions/setup-node@v7
|
|
with:
|
|
node-version: '24'
|
|
registry-url: 'https://registry.npmjs.org'
|
|
package-manager-cache: false # never use caching in release builds
|
|
|
|
- name: Install dependencies
|
|
run: pnpm install --frozen-lockfile
|
|
|
|
- name: Build
|
|
run: pnpm run build
|
|
|
|
- name: Lint
|
|
run: pnpm run lint
|
|
|
|
# The `compat` vitest project inside `pnpm test` stages the REAL harness
|
|
# sources at every supported baseline tag (tests/baselines.ts is the
|
|
# source of truth — keep this fetch list in step when a baseline is
|
|
# added) and runs the built plugin through them; it skips silently
|
|
# without the tags, so this fetch sits BEFORE Test. Only the tags are
|
|
# fetched, so the clone stays shallow.
|
|
- name: Fetch the dsh baseline tags
|
|
run: |
|
|
mkdir -p .tmp/dsh-repo
|
|
cd .tmp/dsh-repo
|
|
git init -q
|
|
git remote add origin https://github.com/deepseek-ai/deepseek-harness.git
|
|
git fetch --depth 1 -q origin \
|
|
refs/tags/dsh-v0.1.5-rc.1:refs/tags/dsh-v0.1.5-rc.1 \
|
|
refs/tags/dsh-v0.1.7-rc.2:refs/tags/dsh-v0.1.7-rc.2
|
|
|
|
- name: Test
|
|
run: DSH_REPO="$PWD/.tmp/dsh-repo" pnpm test
|
|
|
|
- name: Verify version matches the tag
|
|
run: |
|
|
TAG="${{ github.ref_name }}"
|
|
VER="v$(node -p "require('./package.json').version")"
|
|
if [ "$TAG" != "$VER" ]; then
|
|
echo "::error::tag $TAG does not match package version $VER"
|
|
exit 1
|
|
fi
|
|
|
|
# Trusted publishing (OIDC) — no NODE_AUTH_TOKEN required; npm >= 11.5.1
|
|
# exchanges the Actions OIDC token for a short-lived publish credential
|
|
# and attaches provenance automatically.
|
|
- name: Publish to npm
|
|
run: npm publish
|