joaoh82 / rust_sqlite / 26743296261
69%

DEFAULT BRANCH: main
Ran
Jobs 1
Files 62
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 68.985%. Remained the same
26743296261

push

github

web-flow 
fix(release): scope published crate with include allowlist (fixes crates.io 413) (#154)

The `sqlrite-engine` crate publish for v0.11.0 was rejected by crates.io:

  status 413 Payload Too Large: max upload size is: 10485760

The package root is the workspace root and the engine [package] had no
`include`/`exclude`, so `cargo publish` swept the ENTIRE repo tree —
every sibling member plus `web/`, `images/`, and the journal example's
demo media. After SQLR-42 (web/public/playground/pkg/*.wasm, 2.1 MiB)
and SQLR-43 (examples/desktop-journal/docs/demo.gif 9 MiB + demo.mp4
8.7 MiB + screenshots) landed since v0.10.2, the uncompressed tarball
hit ~25 MiB and blew the 10 MiB cap. Patch releases before that stayed
under the limit, which is why this is the first time it broke.

Fix: add an `include` allowlist so only the library/REPL sources, the
three declared `[[example]]` targets (their .rs files must be in the
tarball or `cargo publish`'s verify step can't parse the manifest), and
the readme/license ship. An allowlist beats `exclude` here because new
large files anywhere in the repo can't silently re-bloat the crate.

Verified locally: `cargo package -p sqlrite-engine` produces a 376 KiB
.crate (down from ~25 MiB uncompressed) and the packaged crate compiles
clean against the already-published sqlrite-ask 0.11.0.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

11357 of 16463 relevant lines covered (68.98%)

1.24 hits per line

Jobs
ID Job ID Ran Files Coverage
1 26743296261.1 62
68.98
 GitHub Action Run
Source Files on build 26743296261