bvandeusenandClaude Opus 5.5
5989ffc1c6
CI & Build / Build now, or wait for Android? (push) Successful in 4s
Android / Build, or is the channel already serving this? (push) Successful in 4s
CI & Build / Python lint (push) Successful in 2s
CI & Build / Web typecheck and unit tests (push) Successful in 12s
Desktop (Tauri) / Build, or is the channel already serving this? (push) Successful in 2s
CI & Build / Python tests (push) Successful in 13s
CI & Build / integration (push) Successful in 48s
CI & Build / Build & push image (push) Skipped
Desktop (Tauri) / Web tests, clippy, Rust tests and rustfmt (push) Successful in 4m26s
Desktop (Tauri) / Windows installer (cross-compiled) (push) Successful in 3m32s
Desktop (Tauri) / Tauri desktop (Linux) (push) Successful in 4m10s
Desktop (Tauri) / Update manifest (push) Successful in 4s
Android / Kotlin + Rust (APK) (push) Successful in 12m42s
Export and Import were a link to the server and a reject("needs a server") on the
desktop. Both now run in the core with no server:
- core/src/local/portable.rs builds the same zip the server writes (notes.json,
a Markdown file per note, each attachment this device holds) and reads either
export marker or a Google Keep Takeout zip, with the server's decompression
budget and an all-or-nothing transaction. Export saves to Downloads (no new
plugin) and the sidebar says where; Import takes the archive as raw IPC bytes.
- core/testdata/portable.json pins the format for both copies: the server runs
its Keep and native readers against it (test_portable_fixture.py) and checks
its real export's keys (test_integration.py); the core runs the same cases.
- Found on the way: both importers skipped a Keep note that is only a photo as
"empty". It now imports, on the server and in the core.
- New dependency, approved: `zip` (deflate only) plus `flate2` on its pure-Rust
backend, both already in the lockfile.
The AppImage applications-menu toggle moves from Account, which the desktop
never shows, to the Sync page; the first-run prompt now says so.
errorMessage (#5236) replaces the hand-rolled `.error ?? …` / `.message ?? e`
reads at the remaining catch sites, so a desktop failure shows its real reason.
Task #5170.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
55 lines
3.1 KiB
TOML
55 lines
3.1 KiB
TOML
[package]
|
|
name = "inkwell-core"
|
|
version = "0.1.0"
|
|
description = "Inkwell client core — local-first SQLite store and opt-in sync engine"
|
|
authors = ["bvandeusen"]
|
|
edition = "2021"
|
|
|
|
[dependencies]
|
|
serde = { workspace = true }
|
|
serde_json = { workspace = true }
|
|
log = { workspace = true }
|
|
# Local-first store (M10.4): bundled = compile SQLite in, so there's no system
|
|
# libsqlite dependency to vary across the AppImage / native / Windows / Android builds.
|
|
rusqlite = { version = "0.32", features = ["bundled"] }
|
|
uuid = { version = "1", features = ["v4"] }
|
|
# RFC3339 timestamps for created_at/updated_at/remind_at (Date.parse-able on the JS side).
|
|
chrono = { version = "0.4", default-features = false, features = ["clock"] }
|
|
# HTTP for the opt-in server handshake (M10.6) and the sync engine (M10.7).
|
|
#
|
|
# native-tls, NOT rustls, deliberately: on x86_64-pc-windows-msvc native-tls resolves
|
|
# to `schannel` — pure-Rust bindings to the OS TLS stack — so nothing C or assembly
|
|
# has to cross-compile on the Windows lane, which is the fragile one. rustls would
|
|
# instead pull in ring/aws-lc-rs and their assembler. On Linux native-tls uses
|
|
# OpenSSL, whose headers (libssl-dev) ci-tauri already ships.
|
|
# default-features off drops http2/charset we don't need for a JSON API.
|
|
reqwest = { version = "0.12", default-features = false, features = ["json", "native-tls"] }
|
|
# Verifying downloaded attachment bytes against the sha256 the server advertised.
|
|
sha2 = "0.10"
|
|
# Export and import with no server (local/portable.rs): the same zip the server
|
|
# writes and reads, so a backup crosses between surfaces. Deflate only — every
|
|
# other method (bzip2, zstd, lzma, AES) is off, since neither the server's exports
|
|
# nor Google Takeout use them and several pull in C code.
|
|
zip = { version = "4", default-features = false, features = ["deflate-flate2"] }
|
|
# zip's deflate goes through flate2, which needs a backend chosen. miniz_oxide
|
|
# (`rust_backend`) is pure Rust, so the Windows and Android cross-compiles stay
|
|
# free of C; both crates were already in the lockfile, via the updater and png.
|
|
flate2 = { version = "1", default-features = false, features = ["rust_backend"] }
|
|
|
|
# Android has no system OpenSSL to link against, and `native-tls` resolves to
|
|
# OpenSSL there — unlike Windows, where it lands on schannel and costs nothing.
|
|
# Without this the build dies at `openssl-sys`: "Could not find directory of
|
|
# OpenSSL installation".
|
|
#
|
|
# `vendored` compiles OpenSSL from source with the NDK toolchain. The alternative
|
|
# was rustls on Android only, which builds faster — but rustls ships its own root
|
|
# store, so the phone would trust a DIFFERENT set of certificates than the desktop
|
|
# does. A self-hosted server behind a private or enterprise CA would then work on
|
|
# one surface and fail on another, and "the surfaces behave the same" is worth more
|
|
# than build minutes.
|
|
#
|
|
# Declared as a direct dependency purely to turn the feature on: cargo's feature
|
|
# unification applies it to the copy `native-tls` pulls in transitively.
|
|
[target.'cfg(target_os = "android")'.dependencies]
|
|
openssl-sys = { version = "0.9", features = ["vendored"] }
|