release: 0.3.0 - #73
Merged
Merged
Conversation
The OpenAI Responses API (#70) moves from Unreleased to 0.3.0. It is also the first image since 0.2.0, so it carries 0.2.1's dependency update, which was never tagged or imaged. package.json and the lockfile's own version move to 0.3.0 so release.yml accepts the v0.3.0 tag; the release notes extract as the 0.3.0 section alone (scripts/release-notes.mjs 0.3.0).
sprayberry-redline
approved these changes
Sep 22, 2026
sprayberry-redline
left a comment
sprayberry-redline
left a comment
Collaborator
There was a problem hiding this comment.
Automated review from the Sprayberry Labs fleet code reviewer.
Reviewed by the GPT gating lane (gating review).
Verdict: Approve — no blocking issues found in the release-version and changelog update.
I checked that the root package and lockfile package versions consistently move from 0.2.1 to 0.3.0, and that the changelog release heading precedes its released content while leaving Unreleased available. CI is green (CodeQL, JavaScript/TypeScript analysis, Docker build, tests, and triage).
What's good: the PR intentionally leaves deployment documentation on the currently published image tag until the new signed image exists, avoiding a quickstart that references an unavailable image.
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
2 participants
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.
Cuts 0.3.0: the OpenAI Responses API redaction (#70) moves from
[Unreleased]to[0.3.0] - 2026-09-22.package.jsonand the lockfile's own version go to0.3.0, sorelease.ymlaccepts thev0.3.0tag. It refuses a tag that doesn't match. The lockfile's fastify dependency that also reads 0.2.1 is unchanged.node scripts/release-notes.mjs 0.3.0extracts the 0.3.0 section alone (intro and Added, stopping before 0.2.1), and_test_release_notes.mjspasses.After merge: push
v0.3.0to build the signed multi-arch image on GHCR. Once it's public, a follow-up points the README quickstart anddocs/deploy.mdfromv0.2.0tov0.3.0. They stay on v0.2.0 until then so the quickstart never names an image that doesn't exist yet.