Record the unreleased changes since 0.4.5 - #140
Merged
Merged
Conversation
main has carried #138, #139 and #122 with no CHANGELOG entry. Beyond the bookkeeping gap, deploy.yml deploys main only when the top heading matches package.json and skips on an Unreleased heading, so main presented as a clean 0.4.5 while carrying three unreleased changes. Restore the section so the deploy signal is honest and the next release cut has something to rename.
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. |
There was a problem hiding this comment.
🟢 Approval recommended
This is a low-risk changelog-only update with no blocking issues.
Pull request overview
Adds an Unreleased section to CHANGELOG.md documenting merged changes #122, #138, and #139.
Changes:
- Documents the
onStderrrestoration. - Records the timeout parsing fix.
- Clarifies benchmark deployment-lane wording.
File summaries
| File | Summary |
|---|---|
CHANGELOG.md |
Adds unreleased entries; a minor nit notes the deployment rationale in the PR description does not match the current workflow. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| @@ -1,5 +1,20 @@ | |||
| # Changelog | |||
|
|
|||
| ## Unreleased | |||
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
mainhas carried three merged changes sincev0.4.5(#138, #139, #122) with no CHANGELOG entry for any of them — the file jumped straight from# Changelogto## 0.4.5 — 2026-09-13.That is not just a bookkeeping gap.
deploy.ymldeploysmainonly when the top CHANGELOG heading matchespackage.json; an— Unreleasedheading skips deploy. With the top heading still## 0.4.5andpackage.jsonstill0.4.5,mainpresents as a clean, released 0.4.5 while actually containing three unreleased changes. Adding theUnreleasedsection restores that signal and is a prerequisite for the next release cut, which renames this heading to the new version.Entries added, one per merged PR:
onStderrhook. Called out as a breaking-change restoration because it shipped publicly through v0.4.1 and the removal is contained in v0.4.3–v0.4.5; the package shipsdistwith noexportsgate, so deep importers can reach it. It was restored before the removal reached npm (npm still serves 0.4.1).NEEDLEFISH_REVIEW_TIMEOUT_MS.Deployedmarker no longer claims to be the hosted-action/reusable-workflow default.Verification
pnpm check,pnpm lintclean; full suite 962/962