fix(release): close the super-admin key changeset's frontmatter - #1795
Conversation
The same shape as the zod changeset one commit earlier: the package list ran into a blank line and the prose with no second `---`, so `@changesets/parse` refuses the file and the release's version step fails on it. The closing marker is in place and the blank line after the opening one is gone.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
@nextlyhq/adapter-drizzle
@nextlyhq/adapter-mysql
@nextlyhq/adapter-postgres
@nextlyhq/adapter-sqlite
@nextlyhq/admin
@nextlyhq/admin-css
@nextlyhq/blocks-engine
@nextlyhq/blocks-react
@nextlyhq/builder
create-nextly-app
@nextlyhq/eslint-plugin
nextly
@nextlyhq/plugin-form-builder
@nextlyhq/plugin-page-builder
@nextlyhq/plugin-sdk
@nextlyhq/plugin-seo
@nextlyhq/storage-s3
@nextlyhq/storage-uploadthing
@nextlyhq/storage-vercel-blob
@nextlyhq/ui
commit: |
What
Second instance of #1791, one commit later:
.changeset/a-super-admins-key-copies-the-catalogue.md(landed incd9554690) opened its frontmatter and never closed it — the package list runs into a blank line and the prose with no second---.@changesets/parserefuses the file, sopnpm changeset statusfails onmainandrelease.yml's version step will fail on it.Closing marker added after the 25th package line; the blank after the opening marker removed — the shape every other changeset has. One line.
#1794 edits this file's prose further down (from line 45); the hunks do not overlap, so it merges either way. If that branch also closes the frontmatter, its rebase conflicts on this one line — resolve to either, they are identical.
Evidence
echo .changeset/a-super-admins-key-copies-the-catalogue.md | node scripts/release/check-changesets.mjs→Checked 1 changeset(s): all cover the group..changeset/*.mdonorigin/mainfor fewer than two---lines: this was the only one left after fix(release): close the zod changeset's frontmatter #1791.No changeset of its own: this edits release metadata only.