chore(deps): bump turso_core 0.5.3 → 0.6.0#1636
Open
chaliy wants to merge 1 commit into
Open
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
bashkit | e9b6693 | Commit Preview URL Branch Preview URL |
May 18 2026, 02:21 PM |
Stable release; sticks to GA versions instead of jumping to 0.7 pre-releases. Latest pre-release is 0.7.0-pre.1; if/when a stable 0.7 lands we can bump again. Transitive churn in the lockfile: `built` dropped (no longer pulled by turso), `paste 1.0.15` → `pastey 0.2.2` (turso switched proc-macro helper). Supply-chain exemptions updated to match. Refreshed the two "Turso 0.5.3" version breadcrumbs in spec + diff test comment. API surface we depend on (`Database`, `Connection`, `Value`, `IO`, `File`, `OpenFlags`, `StepResult`, `Buffer`, `Completion`, `CheckpointMode`, `LimboError`, `FileSyncType`) is unchanged — no source edits required. Note on #1634: this bump does NOT unify the RustCrypto split — turso 0.6.0 still pulls `aes-gcm 0.10.3`, which keeps `crypto-common 0.1`, `cpufeatures 0.2`, and the 0.10 `digest`/`sha*` line alongside the workspace's 0.11 cohort. The issue remains blocked on `aes-gcm 0.11` upstream (or turso replacing it).
chaliy
force-pushed
the
claude/ship-turso-upgrade-NWyC8
branch
from
e2329f0 to
e9b6693
Compare
chaliy
changed the title
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.
Summary
Bump
turso_core(andturso_ext/turso_macros/turso_parser) from0.5.3 → 0.6.0 — latest stable release on crates.io. Skipped the
0.7.0-pre.1 pre-release to stay on GA versions.
What changes
Cargo.toml:turso_core = "0.5"→"0.6"Cargo.lock: 4×turso_*bumps;built 0.7.5removed (no longerpulled transitively);
paste 1.0.15→pastey 0.2.2(turso switchedproc-macro helper).
supply-chain/config.toml: matching exemption updates (dropbuilt,rename
paste→pastey, bump turso entries).specs/sqlite-builtin.mdand the
recursive_cte_unsupported_in_tursodivergence note.No source-code changes — the API surface we depend on (
Database,Connection,Value,IO,File,OpenFlags,StepResult,Buffer,Completion,CheckpointMode,LimboError,FileSyncType) is unchanged.Verification
cargo build -p bashkit --features sqlite— greencargo clippy --all-targets --features sqlite -- -D warnings— greencargo fmt --check— greencargo test -p bashkit --features sqlite --lib builtins::sqlite—100 passed
cargo test -p bashkit --features sqlite --test sqlite_differential_tests—19 passed (incl. the
recursive_cte_unsupported_in_tursodivergence pin — turso 0.6.0 still rejects
WITH RECURSIVE)Related — #1634
This bump does not close #1634
(RustCrypto stack split). Turso 0.6.0 still depends on
aes-gcm 0.10.3,which keeps
aes 0.8,cipher 0.4,ctr 0.9,crypto-common 0.1,and
cpufeatures 0.2in the tree alongside the workspace's 0.11cohort. The split remains blocked on either an
aes-gcm 0.11releaseupstream or turso replacing
aes-gcm. #1634 stays open.Test plan