bowenliang123
33068ee1c9
The install/runtime compatibility floor moves from 0.1.1-rc2+ and 0.1.2-alpha2+ to 0.1.2-rc.1+. The 0.1.1 line and the 0.1.2-alpha previews leave the support matrix, so every pre-0.1.2 fallback they existed for is removed outright: - client history: drop the legacy `connection.api.sessions.history` face, the `result`-nested envelope, and the `events` rows field — the gateway `remote.session.page` face and its ClientResult envelope are the only served shapes. - client image loader: drop the pre-0.1.2 `conversation.resolveImage` face; `uiConversation.imageUrl` only. - client node join: drop the pre-0.1.2 `useSession.nodes` seat; `useChat`'s ChatSnapshot `legacy.nodes` only (UseSessionLike removed). - tests/baselines.ts: single baseline `v0.1.2-rc.1`; HostSeam dropped (the registry generation hard-codes header-passing init and seq-0 eager seeding, now mirrored with the exact `init(header, inheritedEventCount)` arity); ClientSeam slimmed to the consumed probes. - deps: devDeps re-pinned to the 0.1.2-rc.1 generation (types compile against the real rc.1 surfaces); cordis ^4.0.2 and schemastery ^3.18.2 per the rc.1 peer requirements; dsh-scope/dsh-invariants declared as dev deps; peer floors >=0.1.2-rc.1; dshReleases table trimmed. - release workflow fetches only the dsh-v0.1.2-rc.1 tag; docs updated (AGENTS.md, README, docs/compatibility.md). - verified against the rc.1 sources: the tool-attribution map (names and packages, incl. the documented `subagent_fork` alias), MCP naming, the page/imageUrl/legacy.nodes faces, and the registry contract.
74 lines
2.4 KiB
YAML
74 lines
2.4 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
|
|
uses: bowenliang123/dsh-plugin-checker@v1
|
|
|
|
# Reads the pinned pnpm version from `packageManager` in package.json.
|
|
- uses: pnpm/action-setup@v6
|
|
|
|
- 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.2-rc.1:refs/tags/dsh-v0.1.2-rc.1
|
|
|
|
- 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
|