chore(release): drop pending changesets to publish 0.13.0#1105
Conversation
main is at 0.13.0 (bumped by the #1096 release-PR merge) but 0.13.0 was never published: the verify-deps release bug (fixed in #1104) made the post-merge run open a 0.13.1 PR instead of publishing. These two changesets remained on main, keeping changesets/action on the version path. Removing them makes the next Release run take the publish path and ship the already-versioned 0.13.0 with its full changelog, tags, and GitHub releases. They are restored in the follow-up 0.13.1 PR.
|
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
emdash-perf-coordinator | 2103c9b | May 19 2026, 07:06 PM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
emdash-i18n | 2103c9b | May 19 2026, 07:06 PM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
docs | 2103c9b | May 19 2026, 07:07 PM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
emdash-demo-cache | 2103c9b | May 19 2026, 07:08 PM |
@emdash-cms/admin
@emdash-cms/auth
@emdash-cms/blocks
@emdash-cms/cloudflare
emdash
create-emdash
@emdash-cms/gutenberg-to-portable-text
@emdash-cms/x402
@emdash-cms/plugin-ai-moderation
@emdash-cms/plugin-atproto
@emdash-cms/plugin-audit-log
@emdash-cms/plugin-color
@emdash-cms/plugin-embeds
@emdash-cms/plugin-forms
@emdash-cms/plugin-webhook-notifier
commit: |
There was a problem hiding this comment.
Pull request overview
Removes the two leftover changeset files on main so that the next Changesets release run takes the publish path and ships the already-versioned 0.13.0 to npm. The changesets will be restored in a follow-up PR to drive the subsequent 0.13.1 release.
Changes:
- Delete
.changeset/ready-worlds-rush.md - Delete
.changeset/fix-local-media-id-normalization.md
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .changeset/ready-worlds-rush.md | Removed so no pending changesets remain, enabling the publish path. |
| .changeset/fix-local-media-id-normalization.md | Removed for the same reason; will be restored in the 0.13.1 follow-up PR. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
emdash-playground | 2103c9b | May 19 2026, 07:10 PM |
Restores the two changesets removed in #1105 (which existed only to flip changesets/action onto the publish path for the already-versioned 0.13.0). With 0.13.0 now published, these re-enter the version path: the next Release run bumps 0.13.0 -> 0.13.1 and refreshes the changeset-release PR (#1103), whose merge publishes 0.13.1 with the #1100/#1101 fixes documented. Files are byte-identical to their pre-#1105 state.
What does this PR do?
Release recovery — this PR triggers the
0.13.0npm publish. Merging it ships0.13.0.mainis already at0.13.0(the #1096 release-PR merge bumped versions and wrote the full## 0.13.0changelogs), but0.13.0was never published: theverifyDepsBeforeRunrelease bug (fixed in #1104) made every post-merge release run die before publishing, so changesets/action opened a fresh0.13.1PR (#1103) instead. Two changesets —fix-local-media-id-normalization.md(#1100) andready-worlds-rush.md(#1101) — were left onmain, which keeps changesets/action on the version path forever.This PR removes only those two changeset files. Nothing else changes:
package.jsonstays at0.13.0, the## 0.13.0changelog sections stay intact. With zero changesets onmain, the next Release run takes the publish path:pnpm changeset publishships0.13.0to npm, pushes thepkg@0.13.0tags, and changesets/action creates the GitHub Releases from the full## 0.13.0notes (including the breaking sandboxed-plugin change from #1057).The two removed changesets are restored verbatim in the immediate follow-up PR, which will release
0.13.1(the #1100/#1101 fixes) on top of the now-published0.13.0.This is the only mechanism by which
0.13.0gets a proper, fully-noted release; it cannot be recovered after the fact.Closes #
Type of change
Checklist
pnpm typecheckpasses (N/A — removes 2 changeset files, no code)pnpm lintpasses (N/A — no code)pnpm testpasses (N/A — no code)pnpm formathas been run (N/A — no code)0.13.0publish; restored in the0.13.1follow-up)AI-generated code disclosure
Screenshots / test output
After merge, the Release run should log
node .github/scripts/release.mjs publish→pnpm changeset publishpublishing0.13.0, withpublished: trueand GitHub Releases created for each package at0.13.0.npm view emdash versionshould go0.12.0 → 0.13.0.