Skip to content

franken-snowflake v0.0.2

Choose a tag to compare

@Dicklesworthstone Dicklesworthstone released this 25 Aug 01:03
· 82 commits to main since this release

13 commits since v0.0.1 (2026-06-30). Patch bump: standalone buildability, one connector fix, repository hygiene, dependency currency. No API changes.

Crates remain publish = false by design — this ships as a GitHub Release only, never to crates.io.

Highlights

  • FrankenSuite dependencies resolve from crates.io instead of local paths, so the workspace builds outside the development fleet; the build preflight is no longer needed.
  • Snowflake connector accepts typed query options.
  • Planning docs, RELEASE.md, and scratch artifacts reorganised; agent-identity leaks dropped.

Dependencies — two pinned families held uniform on purpose

A bare cargo update floats both off-pin:

  • asupersync is pinned =0.3.5 but asupersync-macros drifts to 0.3.10 — held at 0.3.5.
  • the fsqlite family moved 0.1.13 to 0.1.16 while fsqlite-error drifts to 0.1.19 — held at 0.1.16 so all 20 members share one version.

Both were corrected with cargo update -p <crate> --precise <version> rather than by relaxing a pin.

Gate

  • cargo clippy --workspace --all-targets -- -D warnings: clean
  • cargo test --workspace: 420 passed, 0 failed across 32 targets

Artifacts

Each archive contains both franken-snowflake and the short alias fsnow.

asset arch glibc
aarch64-apple-darwin Mach-O arm64 -
x86_64-apple-darwin Mach-O x86_64 -
aarch64-unknown-linux-gnu ELF aarch64 2.28 floor
x86_64-unknown-linux-gnu ELF x86-64 2.28 floor

Both Linux binaries are pinned to a glibc 2.28 floor rather than inheriting the build hosts glibc (2.42), so they run on older distributions.

Every archive was extracted and checked before upload for architecture (file), glibc floor (objdump -T), presence of both binaries, and — because a stale checkout can otherwise ship old code under a new tag — the version the binary itself reports.

Not included

No Windows assets this release. install.sh resolves only linux and darwin triples, so the documented install path is unaffected.