Repository navigation
release: 1.4.2 - #30
Merged
Merged
Conversation
SQLITE_JS_VERSION is what the release is tagged with and what sqlitejs_version() reports, so this is the whole of it: the release job reads make version, finds it differs from the latest release, and tags, publishes and releases under it. The changelog's Unreleased section becomes 1.4.2 and gains a note on the one change that can alter the behavior of JavaScript that works on 1.4.1. A patch release: one behavior change, narrow and in a corner that never worked as it looked -- a db.exec result set read after the call that created it returned -- and five fixes, two of them for crashes. Nothing added and nothing removed, so not 1.5.0. The built library reports 1.4.2 and the suite passes 16 of 16 on macOS arm64. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
SQLITE_JS_VERSIONinsrc/sqlitejs.hgoes from 1.4.1 to 1.4.2, and the changelog's[Unreleased]section becomes[1.4.2] - 2026-11-13with a note on the one behavior change.That is the whole of the release: the
releasejob readsmake version, sees it differs from the latest release's name (1.4.1), and does the rest.What merging this sets off
The push to
mainruns the 14 build jobs and thenrelease, which:ai.sqlite:js:1.4.2;@sqliteai/sqlite-jsand its 7 platform packages) at 1.4.2;Package.swiftwith the 1.4.2 xcframework URL and checksum and pushes that as an[auto-update]commit tomain;1.4.2, which is also the tag, with the platform archives attached andmake_latest: true;flutter-package.yml, which publishessqlite_js1.4.2 to pub.dev.All of that is public and not easily undone, so it is worth being sure of the number before this merges.
Why 1.4.2 and not 1.5.0
Nothing was added and nothing was removed. One change can alter the behavior of JavaScript that works on 1.4.1 — a
db.exec()result set no longer outlives the call into JavaScript that created it — and it is narrow, and in a corner that never worked as it looked: such a result set held a read transaction open, kept an interrupt in effect until the connection closed, and leaked the connection. The rest is five fixes, two of them for crashes.The version inside the library
SQLITE_JS_VERSIONis the single source of truth. The release tag comes from it (tag_name: ${{ steps.tag.outputs.version }}, frommake version), the npm packages' version comes from it, the Maven coordinate comes from it, andflutter-package.ymltakes the pubspec version from the tag.sqlitejs_version()andjs_version()return it. The stale numbers inpackages/node/package.json(1.1.14) andpackages/flutter/pubspec.yaml(1.2.3) are placeholders that the release job overwrites at publish time, so they are not sources of truth.Checked on the build of this branch:
🤖 Generated with Claude Code