Files
dsh-context/.github/workflows/release.yml
T
bowenliang123 74117d8ae5 feat(compat): support dsh 0.2.0-rc.2 as a third baseline
Add dsh-v0.2.0-rc.2 to the supported set alongside the 0.1.5-rc.1 and
0.1.7-rc.2 lines: the manifest's dshReleases, the baseline matrix, the
release workflow's tag fetch, and the compatibility docs.

Every seam the plugin rides is spelled as at 0.1.7-rc.2 - the projection
registry contract, the platform module table, the right Sidebar seats and
guide-entry contract, the session-jump verb pair, the detail channel RPC
faces, the Plugins page card slot over the configForms transport, the
balance settings faces, the step-boundary guard, and the durable event
vocabulary (still the V4 log generation, no v4-to-v5 migration). Cordis
stays 4.0.4 and the dsh peers stay >=0.1.5-rc.1.

Verified on the new tag: all 25 compat-matrix probes pass against the real
harness sources and the vendored cordis, `pnpm run lint:fix && pnpm run
test && pnpm run build` is green (1837 tests, 100% per-file coverage), and
on a disposable DSH_HOME the 0.2.0-rc.2 CLI installs dsh-context@0.60.0
into exactly one composed config row and removes it back to zero.

Also refresh the docs' verification stamp (plugin 0.58.0 -> 0.60.0).
2026-09-29 19:38:55 +08:00

85 lines
3.0 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.2.0-rc.2), whose npm
# dependency closure is complete; `latest` still serves the other
# supported line (0.1.7-rc.2). The 0.1.5-rc 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
# 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 \
refs/tags/dsh-v0.2.0-rc.2:refs/tags/dsh-v0.2.0-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