dsh-local-plugins 0.3.0

Added

• Squash my changes. An agent (Creator mode) collapses all your commits on local into one commit on top of the original release, so the next update merges cleanly. It makes a lpm-backup/pre-squash-* branch first, refuses while an update is unfinished or when upstream is ahead, and must show that the code is byte-for-byte unchanged. The button appears when you have changes versus the original. API: agentDraft mode squash.
• Apply override. In Dependency overrides, one button saves the override, applies it and verifies it: the committed package.json, the live deployment and the installed dependency version must all agree. The dialog shows ✔ Verified or what is wrong. API: applyDep.

Fixed

• The sidebar badge now opens Settings → Local Plugins when dsh's account package replaces the plain Settings button with an account menu.

dsh-local-plugins 0.2.1 — corrected license text

dsh-local-plugins 0.2.1 — corrected license text

A patch release. No behaviour changes since 0.2.0.

What changed

• LICENSE now contains the exact standard MIT text. The file shipped in 0.1.0 and 0.2.0 had a garbled warranty paragraph and was missing the standard limitation-of-liability clause, so GitHub did not recognise the license. The license itself — MIT, as declared in package.json — is unchanged. A published npm version cannot be edited, which is why this is a new release.
• screenshots.json is included so plugin storefronts can show the documentation screenshots.
• The release checklist and compatibility heading are brought up to date.

Install

dsh plugin --profile web add github:ishanshmalviya5/dsh-local-plugins

or npm install dsh-local-plugins. Restart dsh web, then open Settings → Local Plugins. Needs Node 26+, git and npm, on macOS or Linux (Linux: unit tests and package checks pass in CI; not yet verified end to end against a real dsh).

Upgrading from 0.2.0

Nothing to do.

Full details: CHANGELOG · README

Attached package

dsh-local-plugins-0.2.1.tgz — built from the tagged commit and validated by npm run check:package.
SHA-256: 80c9e3959685e2232ecb913f6a7c984ce98fd783b07a459eef5db140eee4a223

dsh-local-plugins 0.2.0 — hardening release

dsh-local-plugins 0.2.0 — hardening release

Customize any dsh plugin — even a built-in one — and keep your changes safe through updates, crashes and dsh upgrades. 0.2.0 keeps the same idea as 0.1 and makes it safe to rely on.

Highlights

• Crash-proof. If a change makes dsh crash, it is rolled back automatically, your work is saved, and a popup tells you what happened. Every apply is recoverable from any point of failure.
• Never half-done. Only a fully built, checked version is switched on; if anything fails, the previous one keeps running.
• Asks before running scripts. Install and build scripts are off by default; you allow them once or always per plugin, and it asks again if the publisher changes.
• Plain status and next steps. Every plugin shows one clear status (Applied, Changes pending, Update available, Conflict, …) and every error says whether your setup is safe and what to do.
• Get back out easily. Unlink restores the original plugin, Delete moves your work to a recoverable trash, Repair installation fixes inconsistencies, and a terminal undo.mjs works even when dsh won't start.
• Exact versions. name@1.2.3, name@tag, or a git #tag / #branch / #commit.
• Agents, safely. Work on it opens an agent in Creator mode inside the plugin's folder with rules that keep it away from your live install.
• Faster: applying a 3000-file plugin went from 17 s to 0.5 s.

Install

dsh plugin --profile web add github:ishanshmalviya5/dsh-local-plugins

Restart dsh web, then open Settings → Local Plugins. Needs Node 26+, git and npm, on macOS or Linux.

Upgrading from 0.1

Automatic and lossless — nothing to do. Your plugins stay exactly as they are; your old registry is kept as a backup file.

What was verified

• 157 unit tests, 15 end-to-end scenarios (75 checks) against a real isolated dsh, a package check that installs the tarball into an empty project, and CI on every pull request.
• macOS (Apple silicon), Node 26: supported. Linux (Ubuntu) passes lint, unit tests and package checks in CI but has not been run end to end against a real dsh. Windows is not supported.

Known limits

A plugin that crashes dsh before this one loads can't be undone automatically (use undo.mjs); the pre-flight check proves files are complete and parse, it does not run the plugin; built-in plugins follow your dsh's bundled version.

Full details: CHANGELOG · README · Security model

Attached package

dsh-local-plugins-0.2.0.tgz — built from the tagged commit and validated by npm run check:package.
SHA-256: 4bfc4b3697bbaac3370354a9da6f0016602e8784c2a7ff4a5bf7da0ef7899494