Repository navigation
chore: require EmDash 1.0.1 or later - #28
Merged
Merged
Conversation
Raise the emdash peer and the manifest's env:emdash floor from >=0.39.0 to >=1.0.1 and move the toolchain to EmDash 1.0.1 (blocks 1.0.1, plugin-test 0.2.6, plugin-cli 0.13.1). The compat matrix now tests the floor only. README and AGENTS lose the 0.x caveats: in-process MCP tools before 0.42 and the English-only in-process pages before 1.0.1. Minor changeset: 0.3.0.
🦋 Changeset detectedLatest commit: 1fc36aa The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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
1 participant
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.
Raises the plugin's EmDash floor from 0.39.0 to 1.0.1, the first stable release. The minor changeset makes the next Version Packages PR analytics 0.3.0. Sites on EmDash 0.39 to 0.42 keep 0.2.x, and a
^0.2.xrange never resolves to 0.3.0.Changes
emdashpeer and the manifest'senv:emdashgo from>=0.39.0to>=1.0.1. It is not>=1.0.0, because npm's accidental April 2026emdash@1.0.0would satisfy that, just as it satisfies today's>=0.39.0.emdashis now^1.0.1(was>=0.39.0 <1.0.0), with@emdash-cms/blocks1.0.1,plugin-test0.2.6 andplugin-cli0.13.1. plugin-test 0.2.6 pins emdash 1.0.1, so thetestsjob now runs on the floor.declared:[1.0.1]instead of seven versions. For now it runs the same thing astests. Once plugin-test moves past 1.0.1, it's the row that keeps the floor tested.pnpm-workspace.yaml: the release-age exclusions list only the versions still installed.scripts/compat-matrix.sh: the default version and the harness-pin example now say 1.0.1.routeCtx.ui?.localefallback.Not changed here:
emdash-release.ymlstill runsplugin-cli@0.12.0throughpnpm dlx. That's the registry release path, and it gets its own change.@emdash-cms/cloudflare@1.0.1and upstreammainstill setsubrequests: 10.Verified
pnpm typecheckpasses,pnpm testpasses (314 tests) andpnpm buildsucceeds.scripts/compat-matrix.sh 1.0.1: 314 passed at the baseline (the harness's pinned host) and 314 at 1.0.1.pnpm peers checkshows one new warning, and it's upstream's: plugin-cli 0.13.1 ships tsdown 0.20.3 alongside TypeScript 6.0.3, and tsdown 0.20.3 declarestypescript ^5. Nothing fails because of it.