Repository navigation
chore(release): prepare 0.24.1 - #1226
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
[Low impact] The changes stay within release metadata, notes, and benchmark records. Retain an empty Changeset before merging so release preparation can pass PR CI. Findings
Fix with agent prompt### Issue 1
packages/hunk/package.json:3
The `0.24.1` version bump consumes every Changeset, including the empty release-preparation marker. PR CI sends this stable release through `changeset:status --since=<base>`, not the generated-prerelease check. That gate requires a retained Changeset, so the release-note check fails. Add an empty Changeset after generating the release.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.SummaryPrepares
benvinegar explicitly acknowledged the required Reviews (1) · Last reviewed commit: "chore(release): prepare 0.24.1" · Reviewed by Greptile |
| { | ||
| "name": "hunkdiff", | ||
| "version": "0.24.0", | ||
| "version": "0.24.1", |
There was a problem hiding this comment.
The 0.24.1 version bump consumes every Changeset, including the empty release-preparation marker. PR CI sends this stable release through changeset:status --since=<base>, not the generated-prerelease check. That gate requires a retained Changeset, so the release-note check fails. Add an empty Changeset after generating the release.
Knowledge Base Used: Distribution and release tooling
Prompt To Fix With AI
This is a comment left during a code review.
Path: packages/hunk/package.json
Line: 3
Comment:
**Release preparation fails CI**
The `0.24.1` version bump consumes every Changeset, including the empty release-preparation marker. PR CI sends this stable release through `changeset:status --since=<base>`, not the generated-prerelease check. That gate requires a retained Changeset, so the release-note check fails. Add an empty Changeset after generating the release.
**Knowledge Base Used:** [Distribution and release tooling](https://app.greptile.com/modem/-/custom-context/knowledge-base/modem-dev/hunk/-/docs/distribution-and-release-tooling.md)
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.There was a problem hiding this comment.
Fixed in b026fad: retained a new empty .changeset/patch-release-preparation.md after version generation. The local verifier and the PR release-note check now pass. The full Firecracker suite was rerun against this final tip and its complete evidence validated.
This comment was generated by Pi using GPT-6.1-sol
Summary
Prepare stable patch release 0.24.1 from main at c3af44f, following v0.24.0.
ExtensionReviewSelection.layoutfield remain documented in the changelog; TypeScript consumers constructing selections must add it.Validation
Using Bun 1.4.4 on Linux x64:
bun install --frozen-lockfilebun run changeset:status(patch only before generation)bun run release:versionbun run generate:changelogbun run bench:releaseandbun run bench:release:compare— pass on full rerunbun run typecheckbun run deps:checkbun run testbun run test:integration— 267 pass, 1 platform skipbun run test:tty-smoke— 11 passbun test ./test/review-conformance— 118 passbun run check:docsbun run check:changelogbun run build:prebuilt:npmbun run check:pack— passes after building the required npm outputbun run check:prebuilt-packbun run smoke:prebuilt-installFull Firecracker compatibility validation passed all 16 scenarios against the clean committed release tip b026fad, followed by successful
validate-release-result.tsverification of the complete evidence and checkout source identity. Local evidence:tmp/install-vm/runs/release-final-OkudporQ/result.json; source identityc98658fb25c3ebf695c1ff960c6deedfdec8a09df5207ff3c1dba60ea2025ca3. The initial run was invalidated by adding the empty CI preparation Changeset; the complete suite was rerun from the final tip rather than reusing that evidence.CI native macOS/Windows compiled portability, Windows compatibility, PTY integration, website, and packaging checks passed. Linux validation initially hit an unchanged timing-sensitive terminal-color watcher test (the 40 ms fence expired before an intermediate assertion); the entire watcher file passes 20 consecutive local repetitions (280 tests). The failed Linux CI job passed on rerun, and all PR checks are now green; no tests or policies were weakened. CI also passed the real Node broker adapter suite.
Publication hold
Do not create/push v0.24.1 or trigger publication until the maintainer explicitly confirms. This PR only prepares metadata and benchmark evidence. Draft editorial release notes are prepared locally; dated website notes and release-media steps follow verified publication.
This PR description was generated by Pi using GPT-6.1-sol