PACKVIUM
    SourceTry it
    RELEASES / PUBLISHED, THEN CHECKED

    What shipped, where it is served, and how you can tell.

    A release is a claim until you can fetch it. Every version here names the registries that serve it and the day that was last observed, and every tag links to the release it was cut from.

    1.1.0CURRENT

    Published
    Registries checked

    The public API is frozen, and the release cut itself.

    • From 1.1.0 the public API, schemas, numeric policy and validation rules do not change without a major version.
    • Every package went out by tag through its own workflow, with a GitHub Release on each of the six mirrors — the first release that did.
    • Both npm packages carry a build-provenance attestation. PyPI files do not: the attestation is filed with GitHub rather than uploaded beside them.
    • @packvium/engine no longer declares the native packages that were never published. Installing it always worked; it now says so.
    • Route-aware unloading landed: a container declares which walls open, and the unload order is decided against them.
    Served by
    Cut from tags
    Build provenance
    • @packvium/engine
    • @packvium/browser

    1.0.0

    Published
    Registries checked

    The stable core, published by hand.

    • Closed the pre-1.0 readiness gate and carried the objective lower bound into all four engines.
    • Convex hulls and compressible items shipped inside it, rather than waiting for a version of their own.
    • It went out by hand: the publish workflow failed, and npm's immutability makes that unrepairable in place. No 1.0.0 artifact will ever carry an attestation.
    Served by
    Cut from tags

    Published by hand. No tag-driven release to link.

    Build provenance

    None. This version predates the tag-driven workflows.

    Before the contract was frozen

    The 0.1.x line, kept as dates. Describing what those versions contain would invite installing one, and the public API only became a promise at 1.0.0.

    • 0.1.3observed on all four registries
    • 0.1.2published
    • 0.1.1published
    • 0.1.0published

    Where these dates come from

    The engine workspace records each release as it closes, and this page reads that record rather than restating it: publication dates, the day the registries were last checked, and which artifacts carry an attestation. A version reaches this page after it is fetchable, not when it is tagged.