Skip to content

Release 1.0.2 - #65

Merged
dentifrag merged 2 commits into
mainfrom
release-1-0-2
Aug 25, 2026
Merged

Release 1.0.2#65
dentifrag merged 2 commits into
mainfrom
release-1-0-2

Conversation

@dentifrag

Copy link
Copy Markdown
Owner

Prepares the 1.0.2 release.

Changes

  • package.json: version 1.0.0 -> 1.0.2
  • CHANGELOG.md: cut the [Unreleased] items into a dated [1.0.2] section, and updated the link refs

Two things worth flagging

package.json was never bumped for 1.0.1. It has said 1.0.0 since 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 a v prefix. That matches the existing 1.0.1 tag, and it also means the Release binaries workflow (which triggers on v*) will not fire and duplicate the build.

Docs-only change, no code touched.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔵 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.json version from 1.0.0 to 1.0.2.
  • Restructure CHANGELOG.md: move Unreleased items into a new 1.0.2 section, add a 1.0.1 section, 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.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟢 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

@dentifrag
dentifrag marked this pull request as ready for review August 25, 2026 21:01
@dentifrag
dentifrag merged commit e1b1366 into main Aug 25, 2026
2 checks passed
@dentifrag
dentifrag deleted the release-1-0-2 branch August 25, 2026 21:02
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.

2 participants