plugins/native/znippy-plugin-rust-toolchain/Cargo.toml
[package]
name = "znippy-plugin-rust-toolchain"
# 0.1.1: local source DRIFTED from the published 0.1.0 at the same version number.
# crates.io bytes are immutable, so the edit only reaches consumers as a new
# version. Bumped 2026-08-23 to unblock the release cascade — holger patches
# znippy to this checkout, which makes 19 holger crates unpublishable fork riders.
version = "0.2.0"
edition = "2024"
description = "Airgapped Rust-toolchain bundle metadata plugin for znippy (native builtin — no WASM)"
license = "MIT"
repository = "https://git.gunnar.rs/nordisk/znippy"
authors = ["Ignalina ApS"]
# Native-only handler: a plain rlib linked into znippy-cli's builtin register.
# Mirrors znippy-plugin-skidbladnir — a compiled-in host handler discovered via
# `meta()`; it does NOT build a cdylib and is NOT compiled to WASM.
[lib]
crate-type = ["rlib"]
[dependencies]
znippy-common = { version = "0.10.0", path = "../../../znippy-common", optional = true }
anyhow = { version = "1", optional = true }
# The znippy handler itself -- the `ArchiveTypePlugin` impl, its Arrow schema and
# its `meta()` discovery record. ON by default, so `znippy-cli`'s builtin register
# and every existing consumer are unchanged.
#
# `--no-default-features` leaves ONLY `src/member.rs`: the pure path->MemberKind
# classifier, which has no dependency at all and therefore compiles for
# `wasm32-unknown-unknown`. That is the seam holger's package-handler plugins take
# -- one classifier for the native handler AND its wasm shim, instead of a second
# copy of the ownership rule in another repo (LAW 5). The technique is
# `znippy-plugin-maven`'s: keep the target-independent core unconditional and put
# the host-only machinery behind a feature that a wasm build turns off.
[features]
default = ["znippy-handler"]
znippy-handler = ["dep:znippy-common", "znippy-common/bundle", "dep:anyhow"]