Publish every surface against the engine fix - #30
Merged
Merged
Conversation
The extension bundles the engine, so a fix to it reaches a user only when the extension is published. This release carries the ones for SQLite databases written by an Android app: a date comparison that answered zero or the whole table without erring, full-text search being refused as unparseable, rowid reported as an invented column, a database copied without its -wal file reporting no tables, and a binary column losing a result set. No extension source changed.
The extension bundles the engine, so a fix reaches its users only when the extension is published. This carries the one for a date comparison against a column that stores a timestamp as a number, which answered zero or the whole table without erring. No extension source changed.
The widget bundles the engine, so it carries the fix only when published. The connectors, server, mcp and react take it as a peer dependency and pick it up on install; they move so every package published in this release is built against the same engine. The lockfile moves with them: it records the workspace versions, so leaving it behind fails the frozen install CI runs.
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
1 participant
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.
Three commits, all versions. The engine fix shipped in
v0.8.0, but three surfaces bundle theengine rather than resolving it at install time, so their users are still running the old one.
@asksql/widgetNo source changed in any surface. The fault they carry is the one where a question about dates against
a column storing a timestamp as a number answered zero, or the whole table, without raising an error -
a 7B model answered 0 where the truth was 2, and a 30B model answered 5.
Verified: TypeScript 3013 passed,
pnpm verifyexit 0,pnpm test:room12/12, frozen lockfile clean.