Repository navigation
ci: release - #4506
ci: release#4506emdashbot[bot] wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
This is the standard automated Changesets release PR, and the approach is correct. It consumes the single pending changeset (fresh-comment-pages.md, an emdash patch from #4460) and moves it into packages/core/CHANGELOG.md. It bumps emdash and the fixed-version packages to 1.4.1 and gives each dependent package a matching patch bump. Both reviewers approved and found nothing that needs fixing. The diff contains no code changes. The reviews were static, and no tests, builds, or publishing commands were run.
Reviewed by anthropic/claude-opus-5-5 and openai/gpt-6.1-sol.
@emdash-cms/admin
@emdash-cms/auth
@emdash-cms/auth-atproto
@emdash-cms/blocks
@emdash-cms/cloudflare
@emdash-cms/contentful-to-portable-text
emdash
create-emdash
@emdash-cms/gutenberg-to-portable-text
@emdash-cms/plugin-cli
@emdash-cms/plugin-test
@emdash-cms/plugin-types
@emdash-cms/registry-client
@emdash-cms/registry-lexicons
@emdash-cms/registry-loader
@emdash-cms/registry-moderation
@emdash-cms/registry-verification
upgrade-emdash
@emdash-cms/sandbox-workerd
@emdash-cms/x402
@emdash-cms/plugin-ai-moderation
@emdash-cms/plugin-ai-search
@emdash-cms/plugin-atproto
@emdash-cms/plugin-audit-log
@emdash-cms/plugin-color
@emdash-cms/plugin-embeds
@emdash-cms/plugin-field-kit
@emdash-cms/plugin-forms
@emdash-cms/plugin-webhook-notifier
commit: |
8d2bec7 to
b7026b4
Compare
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
docs | 908bd1b | Nov 02 2026, 06:28 PM |
e82cb5e to
bb0ad27
Compare
There was a problem hiding this comment.
The automated Changesets release approach remains appropriate. This follow-up incorporates the additional media-upload, forms-editor, dev-runtime, and search-availability release notes while retaining the previously reviewed comment-cache fix.
I checked the follow-up against the current PR diff, consumed changesets, package versions, fixed-version configuration, dependency relationships, and release-note claims against relevant implementation. The current PR remains limited to release metadata and changelogs; implementation changes in the follow-up are already on the base branch. There were no earlier findings to resolve, and I found nothing new that needs fixing.
Static review only; no tests, builds, or publishing commands were run.
Follow-up review by openai/gpt-6.1-sol, scoped to the changes since the last review.
bb0ad27 to
db41a8d
Compare
There was a problem hiding this comment.
The automated Changesets release approach remains appropriate and fits EmDash’s release process.
I checked the follow-up against the full PR diff, consumed changesets, fixed-version configuration, package versions, and dependency relationships. I also verified the newly included seed-taxonomy release notes against the locale-aware lookup, translation-group assignment handling, regression tests, and CLI conflict option. The PR itself remains limited to release metadata and changelogs; implementation and catalog changes visible in the follow-up are already on the base branch.
There were no earlier findings to resolve, and I found nothing new that needs fixing.
Static review only; no tests, builds, or publishing commands were run.
Follow-up review by openai/gpt-6.1-sol, scoped to the changes since the last review.
6266927 to
c506288
Compare
There was a problem hiding this comment.
The automated Changesets release approach remains appropriate and fits EmDash’s release process.
I checked the follow-up against the full PR diff, consumed changesets, fixed-version configuration, package versions, and dependency relationships. I also checked the newly included invite-authentication and plugin-activation release notes against the implementation and regression tests. Implementation and catalog changes in the follow-up are already on the base branch; this PR remains limited to release metadata and changelogs.
There were no earlier findings to resolve, and I found nothing new that needs fixing.
Static review only; no tests, builds, or publishing commands were run.
Follow-up review by openai/gpt-6.1-sol, scoped to the changes since the last review.
c506288 to
4e52e8e
Compare
33d9d77 to
ac96595
Compare
ea50e13 to
87f0cc7
Compare
There was a problem hiding this comment.
The automated Changesets release approach is appropriate and fits EmDash's release process. Both reviewers approved with no findings. The PR is limited to release metadata and changelogs. Package versions, fixed-version alignment, consumed changesets and changelog archive links were checked and are consistent. One reviewer also checked the invite-authentication release note against the middleware, invite route and regression tests. Both reviews were static only; no tests, builds or publishing commands were run.
Reviewed by anthropic/claude-opus-5-5 and openai/gpt-6.1-sol. The change since the last review (1016 lines) was too large for a scoped follow-up, so this is a full review.
3c81f7e to
50dacdc
Compare
There was a problem hiding this comment.
The automated Changesets release approach is appropriate and fits EmDash's release process. Both reviewers approved with no findings. The PR is limited to release metadata: it deletes the consumed changesets, bumps package versions and updates the changelogs. Reviewers checked that the fixed version group moves together from 1.4.0 to 1.4.1 and that the independent packages get matching patch bumps. They also checked the changelog archive links and the docs anchor used by the #4277 entry. One reviewer additionally checked the higher-impact release notes against the implementation and docs. Both reviews were static only. No tests, builds or publishing commands were run.
Reviewed by anthropic/claude-opus-5-5 and openai/gpt-6.1-sol. The change since the last review (1116 lines) was too large for a scoped follow-up, so this is a full review.
50dacdc to
77cc9b2
Compare
There was a problem hiding this comment.
The automated Changesets release approach is appropriate and fits EmDash's release process. Both reviewers approved with no findings. The PR is limited to release metadata: it removes the 33 consumed changesets, bumps package versions, adds changelog entries and rotates the changelog archives. The fixed version group moves together from 1.4.0 to 1.4.1, and the independent packages get matching patch bumps. Archive links resolve, and selected release notes were checked against the implementation and docs. Both reviews were static only. No tests, builds or publishing commands were run.
Reviewed by anthropic/claude-opus-5-5 and openai/gpt-6.1-sol. The change since the last review (1385 lines) was too large for a scoped follow-up, so this is a full review.
77cc9b2 to
270b35c
Compare
There was a problem hiding this comment.
The automated Changesets release approach is appropriate and fits EmDash's release process. Both reviewers approved with no findings, and nothing from the prior review needed to be carried forward. All 36 consumed changesets are removed. The fixed version group moves together from 1.4.0 to 1.4.1, and the independent packages get matching patch bumps. Changelog entries and archive rotations are consistent, and the archive links resolve. The upgrade-guide link in the #4277 KV migration entry resolves to an existing docs heading. Releasing that KV storage migration means deploys need a coordinated upgrade rather than a rolling one. That is a deliberate, documented decision from the source PR. Both reviews were static only. No tests, builds or publishing commands were run.
Reviewed by anthropic/claude-opus-5-5 and openai/gpt-6.1-sol. The change since the last review (1536 lines) was too large for a scoped follow-up, so this is a full review.
1d8f219 to
c1e77d0
Compare
There was a problem hiding this comment.
The automated Changesets release approach is appropriate and fits EmDash's release process. Both reviewers approved with no findings, and the prior review left nothing to carry forward. All 37 consumed changesets are removed, with their descriptions preserved in the affected packages' changelogs. The fixed group moves together from 1.4.0 to 1.4.1, and the independent packages get matching patch bumps. Archive rotations and links are consistent. The plugin KV migration still requires a coordinated upgrade, and the release notes link to migration and recovery guidance. Both reviews were static only; no tests, builds or publishing commands were run.
Reviewed by anthropic/claude-opus-5-5 and openai/gpt-6.1-sol. The change since the last review (1560 lines) was too large for a scoped follow-up, so this is a full review.
c1e77d0 to
d94109f
Compare
There was a problem hiding this comment.
The automated Changesets release is the right approach and fits EmDash's release process. Both reviewers approved with no findings, and the prior review left nothing to carry forward. All 38 consumed changesets are removed, and their descriptions are preserved in the affected packages' changelogs. The fixed group moves together from 1.4.0 to 1.4.1, and the independent packages get matching patch bumps. Archive rotations and links are consistent. The plugin KV migration keeps its coordinated-upgrade warning and links to migration and recovery guidance. Both reviews were static only; no tests, builds or publishing commands were run.
Reviewed by anthropic/claude-opus-5-5 and openai/gpt-6.1-sol. The change since the last review (1565 lines) was too large for a scoped follow-up, so this is a full review.
d94109f to
4f9975b
Compare
There was a problem hiding this comment.
The automated Changesets release is the right approach and fits EmDash's release process. Both reviewers approved with no findings, and the prior review left nothing to carry forward. The fixed group moves together from 1.4.0 to 1.4.1. The independent packages get matching patch bumps. Consumed changesets are removed, and their descriptions are preserved in the affected packages' changelogs. Archive rotation links are consistent. The plugin KV migration keeps its coordinated-upgrade warning and links to migration and recovery guidance. Both reviews were static only; no tests, builds or publishing commands were run.
Reviewed by anthropic/claude-opus-5-5 and openai/gpt-6.1-sol. The change since the last review (1570 lines) was too large for a scoped follow-up, so this is a full review.
4f9975b to
5b4dbe1
Compare
There was a problem hiding this comment.
The automated Changesets release is the right approach and fits EmDash's release process. Both reviewers approved with no findings, and the prior review left nothing to carry forward. The fixed group moves together from 1.4.0 to 1.4.1, and the independent packages get matching patch bumps. Consumed changesets were removed and their text appears in the package changelogs, including the coordinated-upgrade warning for the plugin KV migration. Changelog archive links are consistent. Both reviews were static only; no tests, builds or publishing commands were run.
Reviewed by anthropic/claude-opus-5-5 and openai/gpt-6.1-sol. The change since the last review (1575 lines) was too large for a scoped follow-up, so this is a full review.
4efad68 to
7baf9b6
Compare
7baf9b6 to
908bd1b
Compare
There was a problem hiding this comment.
The automated Changesets release is the right approach and follows EmDash's release process. Both reviewers approved with no findings, and none carry over from the prior review. The fixed group moves together from 1.4.0 to 1.4.1, and the independent packages get matching patch bumps. All consumed changesets use patch. Their text appears in the affected package changelogs, including the coordinated-upgrade guidance for the plugin KV migration. The new changelog archive links are consistent. Both reviews were static only; no tests, builds or publishing commands were run.
Reviewed by anthropic/claude-opus-5-5 and openai/gpt-6.1-sol. The change since the last review (1658 lines) was too large for a scoped follow-up, so this is a full review.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@emdash-cms/admin@1.4.1
@emdash-cms/auth-atproto@0.2.51
@emdash-cms/blocks@1.4.1
@emdash-cms/cloudflare@1.4.1
emdash@1.4.1
@emdash-cms/plugin-cli@0.13.6
@emdash-cms/plugin-test@0.2.12
@emdash-cms/plugin-ai-moderation@0.2.3
@emdash-cms/plugin-ai-search@0.1.1
@emdash-cms/plugin-embeds@0.1.59
@emdash-cms/plugin-field-kit@0.1.3
@emdash-cms/plugin-forms@0.2.13
@emdash-cms/registry-client@0.7.2
@emdash-cms/registry-lexicons@0.7.1
@emdash-cms/registry-loader@0.1.4
@emdash-cms/registry-verification@0.3.5
@emdash-cms/sandbox-workerd@0.9.7
@emdash-cms/auth@1.4.1
create-emdash@1.4.1
@emdash-cms/gutenberg-to-portable-text@1.4.1
@emdash-cms/x402@1.4.1