Release 1.0.2 - #65
Conversation
There was a problem hiding this comment.
🔵 Needs a closer look
The 1.0.2 changelog wording about the server/binaries “targeting Node 22” is ambiguous given the repo’s esbuild --target=node20 configuration and should be clarified before release notes are finalized.
Pull request overview
Prepares the 1.0.2 release by updating the package version and rolling changelog entries forward into dated release sections (including backfilling 1.0.1 for completeness).
Changes:
- Bump
package.jsonversion from1.0.0to1.0.2. - Restructure
CHANGELOG.md: move Unreleased items into a new1.0.2section, add a1.0.1section, and update link references.
File summaries
| File | Description |
|---|---|
| package.json | Updates published version to 1.0.2 for the release. |
| CHANGELOG.md | Cuts a 1.0.2 release section, backfills 1.0.1 notes, and updates compare links. |
Review details
Suppressed comments (1)
CHANGELOG.md:18
- The changelog says the built server and packaged binaries “still target Node 22”, but the repo also builds the server bundle with
esbuild --target=node20, so “target” here is ambiguous/misleading (build target vs runtime base). Consider rephrasing to make the claim unambiguous (e.g., Docker image runs on Node 22 and pkg binaries target node22) while still emphasizing this is dev-toolchain only.
- Raised the development Node.js requirement to `^22.22.2 || ^24.15.0 || >=26.0.0`, following the
jsdom 30 upgrade. This affects the dev toolchain only; the built server and packaged binaries
still target Node 22.
- Files reviewed: 2/2 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
There was a problem hiding this comment.
🟢 Approval recommended
The changes are limited to release metadata/docs, and the updated changelog statements align with the repo’s build/runtime targets (node20 build target, node22 Docker/pkg).
Review details
- Files reviewed: 2/2 changed files
- Comments generated: 0 new
- Review effort level: Lite
Prepares the 1.0.2 release.
Changes
package.json:version1.0.0 -> 1.0.2CHANGELOG.md: cut the[Unreleased]items into a dated[1.0.2]section, and updated the link refsTwo things worth flagging
package.jsonwas never bumped for 1.0.1. It has said1.0.0since the first release, so this bump crosses two versions rather than one. Going to 1.0.2 (not 1.0.1) since the 1.0.1 tag and GitHub release already exist.1.0.1 never got a CHANGELOG section. The file jumped straight from
[Unreleased]to[1.0.0], so the quick-filter feature that shipped in it was undocumented. Backfilled a[1.0.1]section from that release's actual contents (#46, #44) so the history is complete.Why patch and not minor
Everything user-facing since 1.0.1 is a bug fix (#64 right-click menu, #59 folder downloads). The Node.js requirement change (#63) is dev-toolchain only; the built server and packaged binaries still target Node 22, so it does not affect anyone running Siphon.
Release mechanics
Binaries are being built locally rather than on CI to save Actions minutes, then uploaded to the release manually.
The tag will be
1.0.2, without avprefix. That matches the existing1.0.1tag, and it also means theRelease binariesworkflow (which triggers onv*) will not fire and duplicate the build.Docs-only change, no code touched.