LowPack 0.2.1 - safe alpha archive migration
Pre-releaseI thought too on the point that a security-driven format change should not
strand the first LowPack archives. LowPack 0.2.1 adds a narrow, checked bridge
from format 1.0 to the stricter format 1.1 / manifest schema 2.0.
Oh! On this part, I kept reading and writing separate on purpose:
lowpack compatibility old.lpkauthenticates and classifies an archive
without decompressing it or writing anything.lowpack migrate old.lpk -o migrated.lpkleaves the source untouched,
preserves its compressed chunk payloads, validates the converted manifest,
fully reconstructs every file in a temporary archive, and publishes the
destination only after that succeeds.
The README now begins with a real release-wheel installation instead of an
editable developer install. The new getting-started and compatibility guides
cover Windows, macOS, Linux, upgrades, command discovery, checksums, and the
exact migration trust boundary.
Install the release wheel:
python -m pip install "https://github.com/devkyato/Lowpack/releases/download/v0.2.1/lowpack-0.2.1-py3-none-any.whl"
lowpack --version
lowpack doctorWhat I verified before publishing:
- 66 tests passed, with 3 expected platform-specific skips.
- Ruff and strict Mypy passed.
- Linux/Windows CI across Python 3.9 through 3.14 passed.
- The package build, clean wheel install, benchmark smoke, and 5,000-run
manifest fuzz smoke passed in GitHub Actions. - Two isolated builds from merged commit
4000aec6a779eb8c3127ee91a96968b7e3b0f3d2were byte-identical. - The published 0.1.2 wheel created a 23-file source archive with dictionaries;
the 0.2.1 wheel migrated, fully verified, unpacked, and byte-matched all 23
files. - The README cover is byte-for-byte the supplied LowPack cover image.
SHA-256:
b928236e9e21949d4163566bc6e09ad4f5697445e297799fd22d37024e516514 lowpack-0.2.1-py3-none-any.whl
51364e1aa247d57dcb1231ac4127038877b8bb5ef6ad59ef5027fecd80a79460 lowpack-0.2.1.tar.gz
This remains an alpha prerelease. It does not promise unknown future-format
compatibility, repair corrupt archives, stream canonical telemetry transforms,
or replace the need for another copy of important data.
Migration work: issue #3
Implementation and checks: pull request #11
Post-merge CI: run 30459368382