bvandeusenandClaude Opus 5.5
06ed76814f
Android / Build, or is the channel already serving this? (push) Successful in 2s
Desktop (Tauri) / Build, or is the channel already serving this? (push) Successful in 2s
Android / Core and FFI clippy and tests (push) Successful in 55s
CI & Build / Build now, or wait for Android? (push) Successful in 4s
Desktop (Tauri) / Web tests, clippy, Rust tests and rustfmt (push) Successful in 2m25s
CI & Build / Web typecheck and unit tests (push) Successful in 12s
CI & Build / Python lint (push) Successful in 2s
CI & Build / Python tests (push) Successful in 14s
CI & Build / integration (push) Successful in 2m20s
CI & Build / Build & push image (push) Skipped
Desktop (Tauri) / Windows installer (cross-compiled) (push) Successful in 3m29s
Desktop (Tauri) / Tauri desktop (Linux) (push) Successful in 4m27s
Desktop (Tauri) / Update manifest (push) Successful in 4s
Android / Kotlin + Rust (APK) (push) Successful in 9m17s
Android / Build the server image (push) Successful in 1s
#6227 "License Inkwell under AGPL-3.0-only: LICENSE file and SPDX identifier". The operator chose AGPL-3.0-only, as for FabledStash (#6212). - LICENSE is the canonical GNU AGPL v3 text from gnu.org: 661 lines, md5 eb1e647870add0502f8f010b19de32af, the same file as FabledStash's. - AGPL-3.0-only is declared in pyproject.toml, frontend/package.json (and its lockfile root entry), the four crates, and tauri.conf.json's bundle. - The pacman package declared MIT; it now declares AGPL-3.0-only. - pyproject's build floor moves to setuptools>=77, the first release that reads `license` as an SPDX expression. - The README's Licence section names the licence, links LICENSE, and states the network clause in one sentence. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
57 lines
3.1 KiB
TOML
57 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"]
|
|
license = "AGPL-3.0-only"
|
|
edition = "2021"
|
|
|
|
[dependencies]
|
|
serde = { workspace = true }
|
|
serde_json = { workspace = true }
|
|
log = { workspace = true }
|
|
# Local-first store: bundled = compile SQLite in, so there's no system
|
|
# libsqlite dependency to vary across the AppImage / native / Windows / Android builds.
|
|
# functions = the `fold` SQL function tag names are compared and indexed by:
|
|
# SQLite's own lower() folds ASCII only, and the server folds every letter.
|
|
rusqlite = { version = "0.32", features = ["bundled", "functions"] }
|
|
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 and the sync engine.
|
|
#
|
|
# 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. Not rustls on
|
|
# Android, though it builds faster: rustls ships its own root store, so the phone
|
|
# would trust a DIFFERENT set of certificates than the desktop does, and a
|
|
# self-hosted server behind a private or enterprise CA would work on one surface
|
|
# and fail on another.
|
|
#
|
|
# 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"] }
|