4 Commits

Include renames

Author	SHA1	Message	Date
infosave2007	32ce2f7ed7	chore: satisfy CI fmt/clippy gates; make the release publish step idempotent ... `cargo fmt --all -- --check` and `cargo clippy --all-targets -- -D warnings` are CI gates and both were failing on this release's code. - rustfmt across the files touched by the release - `.split('/').last()` walks the whole iterator on a DoubleEndedIterator; use `.next_back()` (4 sites in the setup/featured + delete handlers) - `set_progress` had two identical branches; the intent is "take the first reading, then only move forward", which is one condition release.yml published unconditionally on a version tag, so a version already on crates.io (released by hand, or a re-run of the job) failed the workflow — a version can never be re-uploaded. It now checks the registry and skips instead.	2026-08-06 18:18:21 +03:00
infosave2007	3d71b03788	ci: build Windows binaries; add cross-platform CI test matrix ... - release.yml: add x86_64-pc-windows-msvc target, OS-aware packaging (.exe + .zip) - ci.yml: split into lint (fmt/clippy) + test matrix (ubuntu/windows/macos) - use getrandom for the admin/key token CSPRNG (secure on Windows too)	2026-06-30 14:56:54 +03:00
infosave2007	3b0231b32d	ci(release): use env-mapped token guard for crates.io publish step	2026-06-30 13:54:35 +03:00
infosave2007	fd2f2a165b	chore(release): prepare v0.1.0 for crates.io ... - bump version to 0.1.0; add crates.io metadata (include list, homepage, rust-version) - add .github/workflows/release.yml: on tag v* → publish to crates.io + GitHub Release with binaries - README: absolute links/images and badges so it renders on crates.io; add install section - CHANGELOG: 0.1.0	2026-06-30 13:47:42 +03:00