@eya46/dsh-plugins

pnpm monorepo for DeepSeek Harness plugins.

Package	Description
@eya46/dsh-plugin-info	Settings page for profile-added plugins, updates, and version notes

Install

From npm (published package):

dsh plugin --profile web add @eya46/dsh-plugin-info

From this monorepo (local development):

pnpm install
dsh plugin --profile web add "file:./packages/dsh-plugin-info"

Development

pnpm install
pnpm -r --filter "./packages/**" test          # run tests for every package
pnpm -r --filter "./packages/**" typecheck     # typecheck every package
pnpm -r --filter "./packages/**" build         # build every package

Releases

This monorepo uses changesets to drive versioning, npm publishing, and GitHub releases.

1. Ship a change. Open a PR that touches packages/*, and include a .changeset/<name>.md describing the user-facing change and the semver bump for each affected package:

   ---
   "@eya46/dsh-plugin-info": patch
   ---
   
   Brief, user-facing summary of what changed.
   

2. Merge the PR. The Release GitHub Action opens (or updates) a chore: release packages PR that bumps affected package.json versions and writes per-package CHANGELOG.md entries.
3. Merge the release PR. The same Action publishes the new versions to npm, creates the git tag, and opens a GitHub release with auto-generated notes for each package.

Required GitHub repository secret: none. Publishing uses npm trusted publishing (OIDC): the Release job grants id-token: write, and pnpm 11 (the pinned packageManager) exchanges that OIDC token for a short-lived npm publish token. Each published package must name this repository and workflow as its trusted publisher on npmjs.com — package → Settings → Trusted Publisher → GitHub Actions:

Field	Value
Organization or user	eya46
Repository	dsh-plugins
Workflow filename	release.yml
Environment	(leave empty)

npm also requires a recent pnpm for the exchange, which is why the workspace pins pnpm@11.28.2: pnpm 10 has provenance signing but no trusted-publishing support.