Stop tying the plugin to one dsh line, and ask for Evolver 2.0.39 - #28
Merged
Merged
Conversation
dsh upgrades often, and the peer ranges said `<0.1.7` while 0.1.7-rc.2 is already published. The range never protected anything: dsh's loader does no version check, the profile installs with autoInstallPeers off, and the host hands the plugin its own dsh-llm / dsh-tools / dsh-skill at runtime. What can actually break is the four symbols the plugin imports -- createUserMessage, boundContextSummary, defineTool, BUNDLED_SKILL_RANK -- and all four are still exported in 0.1.7. So the ranges become `>=0.1.5-0`, and the guard moves to where breakage shows up: CI runs the suite against the `next` and `alpha` dist-tags as well as 0.1.5-rc.3, and runs daily, so an incompatible dsh release turns CI red before users upgrade into it. 95/95 pass on 0.1.5-rc.3, 0.1.7-alpha.2 and 0.1.7-rc.2. Evolver is the one dependency that does gate behaviour: a Proxy older than 2.0.39 answers every text recall empty, so priming silently injects nothing. The Proxy status does not carry its version, so the plugin reads `evolver --version` once at boot and, below 2.0.39, the first step of a session carries a notice with the upgrade command -- at most once a day per installed version. No evolver on PATH means no notice; /evolver-status covers that case and now names the minimum too. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The problem
dsh upgrades often. The peer ranges said
<0.1.7, and0.1.7-rc.2is already published — so on paper the plugin no longer supports the dsh users are upgrading to.What the range was actually protecting
Nothing. Checked in
dsh-app-boot:autoInstallPeers: false;dsh-llm/dsh-tools/dsh-skillat runtime (module fallback).What can really break is the API surface the plugin imports — four symbols:
createUserMessageboundContextSummarydefineToolBUNDLED_SKILL_RANKWhat changes
>=0.1.5-0, no upper bound.0.1.5-rc.3plus thenextandalphadist-tags, and runs daily — an incompatible dsh release turns CI red before users upgrade into it, instead of the range going stale again./proxy/statusdoesn't carry a version, so the plugin readsevolver --versiononce at boot; below 2.0.39 the first step of a session carries an upgrade notice (npm install -g @evomap/evolver@latest), at most once a day per installed version. Noevolveron PATH → no notice./evolver-statusnames the minimum too.Verification
95/95 on each of:
0.1.5-rc.30.1.7-alpha.20.1.7-rc.2New tests put a fake
evolveron PATH, so the suite never depends on what the machine has installed.Caveats
>=0.1.5-0doesn't match0.1.7-rc.x. pnpm likely treats prereleases as matching for peer checks, but that is unconfirmed. Either way the worst case is an install-time warning — peers are host-provided. No strict-semver range covers future prereleases.🤖 Generated with Claude Code