Skip to content

chore(release): prepare 0.24.1 - #1226

Merged
benvinegar merged 2 commits into
mainfrom
release/0.24.1
Oct 24, 2026
Merged

benvinegar merged 2 commits into
mainfrom
release/0.24.1

Conversation

@benvinegar

@benvinegar benvinegar commented Oct 24, 2026 •

Copy link
Copy Markdown
Member

Summary

Prepare stable patch release 0.24.1 from main at c3af44f, following v0.24.0.

  • Generate the package version, lockfile, canonical changelog, and website changelog projection using the release tooling; consume all pending Changesets.
  • Include the Bun 1.4.4 security update, Nix highlighting/build fixes, and search-occurrence fix already merged to main.
  • Treat the search Changeset as patch at the maintainer's explicit request. Extension API 32 and the new required ExtensionReviewSelection.layout field remain documented in the changelog; TypeScript consumers constructing selections must add it.
  • Commit the five-sample Linux/x64 release benchmark. The full rerun passes against 0.24.0 without accepted regressions. The first run flagged first-frame latency (13.76 ms vs 8.45 ms); the isolated full rerun measured 7.56 ms. No policy overrides were added.
  • Keep 0.24.1 marked Unreleased on the website until its tag exists.

Validation

Using Bun 1.4.4 on Linux x64:

  • bun install --frozen-lockfile
  • bun run changeset:status (patch only before generation)
  • bun run release:version
  • bun run generate:changelog
  • bun run bench:release and bun run bench:release:compare — pass on full rerun
  • bun run typecheck
  • bun run deps:check
  • bun run test
  • bun run test:integration — 267 pass, 1 platform skip
  • bun run test:tty-smoke — 11 pass
  • bun test ./test/review-conformance — 118 pass
  • bun run check:docs
  • bun run check:changelog
  • bun run build:prebuilt:npm
  • bun run check:pack — passes after building the required npm output
  • bun run check:prebuilt-pack
  • bun run smoke:prebuilt-install
  • Real release diff rendered in a 140×40 PTY with concrete github-dark theme; hunk navigation and quit exercised.

Full Firecracker compatibility validation passed all 16 scenarios against the clean committed release tip b026fad, followed by successful validate-release-result.ts verification of the complete evidence and checkout source identity. Local evidence: tmp/install-vm/runs/release-final-OkudporQ/result.json; source identity c98658fb25c3ebf695c1ff960c6deedfdec8a09df5207ff3c1dba60ea2025ca3. 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

@vercel

vercel Bot commented Oct 24, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
hunk-web Ignored Ignored Preview Oct 24, 2026 5:57pm UTC

Request Review

@greptile-apps

greptile-apps Bot commented Oct 24, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 4/5

[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

  1. P1 Release preparation fails CI ▶
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.

Summary

Prepares 0.24.1 with generated release metadata and benchmark results.

  • Hunk's 0.24.1 release notes appear while the release stays unpublished.
  • The 0.24.1 release has a Linux x64 benchmark record.

benvinegar explicitly acknowledged the required ExtensionReviewSelection.layout type change and stated that the maintainer requested a patch release.

Reviews (1) · Last reviewed commit: "chore(release): prepare 0.24.1" · Reviewed by Greptile

{
"name": "hunkdiff",
"version": "0.24.0",
"version": "0.24.1",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 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

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.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@benvinegar
benvinegar merged commit 5ea1e38 into main Oct 24, 2026
20 of 22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant