Skip to content

Releases: pure-craft/dsh-actions

v0.5.2

Choose a tag to compare

@github-actions github-actions released this 22 Oct 11:50

Full Changelog: v0.5.1...v0.5.2

v0.5.1

Choose a tag to compare

@github-actions github-actions released this 22 Oct 11:31

Full Changelog: v0.5.0...v0.5.1

v0.5.0

Choose a tag to compare

@github-actions github-actions released this 21 Oct 10:56

Full Changelog: v0.4.1...v0.5.0

v0.4.1

Choose a tag to compare

@github-actions github-actions released this 18 Oct 13:59

Full Changelog: v0.4.0...v0.4.1

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 16 Oct 12:00

Full Changelog: v0.3.1...v0.4.0

v0.3.1

Choose a tag to compare

@github-actions github-actions released this 13 Oct 09:28

Full Changelog: v0.3.0...v0.3.1

v0.3.0

Choose a tag to compare

@github-actions github-actions released this 13 Oct 08:37

Full Changelog: v0.2.1...v0.3.0

v0.2.1

Choose a tag to compare

@github-actions github-actions released this 12 Oct 11:25

Full Changelog: v0.2.0...v0.2.1

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 08 Oct 11:05

Full Changelog: v0.1.2...v0.2.0

v0.1.1 — DSH 0.2 install floor, bilingual docs

Choose a tag to compare

@pure-craft pure-craft released this 30 Sep 09:12

DSH Actions v0.1.1

Two things changed: the plugin installs on DSH 0.2 again, and every public doc is now bilingual.

DSH 0.2 support

v0.1.0 declared its peers as ^0.1.7-alpha.2. That range caps at <0.2.0, so it turned away 0.2.0-rc.2 — what the registry's latest points at today. Users on the default channel hit nothing was installed, and a rejected plugin records no download at all.

The peers are now an open floor: >=0.1.7-alpha.1. That number is measured, not guessed:

  • scripts/verify-floor.mjs unpacks the provider packages at a given version and diffs their identifiers against the built bundles — all 31 members lib/client.js renders exist at 0.2.0-rc.2; 0.1.5-rc.3 still misses 20 of them.
  • tests/plugin-peers.spec.ts locks the floor in with the runtime's own semver and guards forward through 0.2.0-rc.2.

Hosts below the floor are still rejected, unchanged. The escape hatch stays per-version-pair:

dsh plugin allow-version dsh-actions@<version> --dsh-version <your DSH version> --accept-risk

Bilingual docs

Every public doc now ships as a pair — Chinese stays the canonical *.md, English lands as the sibling *.en.md in the same directory. That mirrors what README.md / README.en.md already did, and keeps existing URLs working.

  • English mirrors for all 4 feature docs and all 3 scenario docs
  • docs/README.md as a bilingual index, rendered when you browse the docs/ tree
  • every relative link in docs/ replaced with an absolute blob/main URL, every image with a raw.githubusercontent.com URL — these files get read outside the repo too (npm, forks, editor preview)
  • a language switcher line at the top of each Chinese doc

README

Both languages were re-laid out: a full 3×2 screenshot grid instead of the ragged table, "Interface" moved ahead of "Install", a new "Version floor" subsection, a comparison table (ad-hoc vs CLI/MCP vs agent skill vs an actions.json in the project) under Origin, and a tabulated package identity.

407 tests.

Install

cd ~/.dsh/profiles/web && npm install dsh-actions   # then restart DSH Web

Requires DSH >= 0.1.7-alpha.1; the current registry latest (0.2.0-rc.2) satisfies it, so no channel switching. npm: https://www.npmjs.com/package/dsh-actions

Full changelog: v0.1.0...v0.1.1