RELEASES / PUBLISHED, THEN CHECKED
Releases: 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.11.0CURRENT
- Published
- Registries checked
A bag can stand up as a pouch, every objective now states a lower bound, and the four engines agree on money, measures and order.
- A gusseted_bag may declare bottom_gusset_depth, alone or with side_gusset_depth. The bottom panel lengthens the loop the goods must fit round: a 300 mm rod that no flat or side-gusseted 300 x 150 mm bag holds goes into the same bag with a 40 mm bottom gusset, and a second one on top would not fit. orientation: standing packs the bag upright as a pouch, while inner_dimensions still echoes the size you declared.
- shipping_cost and lowest_landed_cost carry optimality.lower_bound and its gap, so all seven objectives now state one. Two committed fixtures report optimal where 1.10 said feasible, with the same placements and scores.
- A four-engine audit pinned what the engines had disagreed on: one money ceiling of 2^53 - 1 minor units, one grammar for a measure, a limit of 32 hull_vertices, and one order in which equally ranked container types open (the code-point order of their ids).
- The reason an item was left out no longer reads a clock, so a busy host can no longer turn insufficient_support into no_feasible_placement. In @packvium/engine, the quality profile no longer crashes with two payload-limited container types, and rating a single ground contact now costs time proportional to the placements on one plane, with byte-identical answers.
- packvium-native is on PyPI: it runs the compiled Rust engine when its platform wheel is installed through the native extra and the pure Python engine otherwise, and backend() says which one answered.
- Changed, in every engine: a rate_table priced above 2^53 - 1 and a measure written as 1e2, 1_00, .5, 5., 0x64 or 100 millimeters are refused, as are more than 32 hull_vertices. A request whose container ids look like numbers can pack differently in PHP and JavaScript, which now order them as Python and Rust do.
Documented in
Served by
- packvium PyPI
- packvium/packvium Packagist
- @packvium/engine npm
- @packvium/browser npm
- packvium-native PyPI
- packvium crates.io
Cut from tags
- packvium/packvium-python v1.11.0
- packvium/packvium-php v1.11.0
- packvium/packvium-node v1.11.0
- packvium/packvium-wasm v1.11.0
- packvium/packvium-rust v1.11.0
- packvium/packvium-python-adapter v1.11.0
- packvium/packvium-native v1.11.0
Build provenance
@packvium/engine@packvium/browser
1.10.0
- Published
- Registries checked
Pallets can carry an overhanging load, three more objectives state a lower bound, and every placement carries an id every engine derives alike.
- A container can declare pallet_overhang_limit: the load may pass the deck by that length at each end and width at each side. Only the deck bears weight, a load the deck holds is never overhung, and the packed pallet reports the size it reached as achieved_dimensions and is billed at it.
- maximum_value, open_dimension_height and maximum_volume carry optimality.lower_bound and its gap, as default and lowest_cost do, so five of the seven objectives can now prove an answer optimal. Five committed goldens now report optimal where 1.9 said feasible, with the same placements.
- Every placement carries placement_id, the canonical JSON of its container, position, item type and orientation; fixed placements, plan revisions and execution plans may quote it. A request may declare its currency, echoed on the result and checked against every rate_table.
- A bag can be gusseted: deformable_boundary {kind: gusseted_bag, side_gusset_depth} widens the width girth by the gusset. Convex hulls accept all 24 proper rotations as signed codes such as -L-W+H. Made-to-measure boxes keep a void-fill reserve, and nested packing can carry the best K chains from one level to the next with level_beam_width.
- Changed: a units key other than length is refused as not_allowed - {length: cm, weight: kg} used to read bare weights as grams. A result without placement_id no longer validates, so check a 1.9 result with the 1.9 validator or pack it again.
Documented in
Served by
- packvium PyPI
- packvium/packvium Packagist
- @packvium/engine npm
- @packvium/browser npm
- packvium crates.io
Cut from tags
- packvium/packvium-python v1.10.0
- packvium/packvium-php v1.10.0
- packvium/packvium-node v1.10.0
- packvium/packvium-wasm v1.10.0
- packvium/packvium-rust v1.10.0
- packvium/packvium-python-adapter v1.10.0
Build provenance
@packvium/engine@packvium/browser
1.9.0
- Published
- Registries checked
The four engines and every validator now agree where 1.8 found them apart, with no schema change.
- Rust and the JavaScript engine check the centre of gravity as Python and PHP do: under a minimum_support_ratio above 0, a box resting on at most half its base with its centroid outside the area it touches is refused. Every validate also checks that rule and the whole stack's load, sharing a box's weight among its bearers by contact area.
- Changed in every engine: a side of zero is refused as must be positive, an obstacle box outside its container as lies outside inner_dimensions, a length past 2^53 - 1 ticks and a weight past 2^63 - 1 ticks as above_maximum, each at its JSON Pointer.
- Breaking in both JavaScript packages: a weight's ticks, and a shipping_cost score position, are a BigInt past 2^53 - 1 ticks, about 1,126 tonnes; stringifyExact and parseExact carry such a result through JSON. Every lighter load gets the same answer and types as in 1.8.
- The JavaScript engine spends effort_budget as the other engines do and reports the milliseconds it took in algorithm.duration_ms, which was always 0; its quality search is about 1.6x faster with no score changed. PHP answers kilometre-scale requests exactly, and its quality search now runs Python's starts.
- Fixed: nesting under a clearance uses the items' own overlap and a deep nesting column nests in pairs, a compressible item bears its load on its own footprint, and the JavaScript engine keeps a ground_contact_rule: single item on one supporter.
Served by
- packvium PyPI
- packvium/packvium Packagist
- @packvium/engine npm
- @packvium/browser npm
- packvium crates.io
Cut from tags
- packvium/packvium-python v1.9.0
- packvium/packvium-php v1.9.0
- packvium/packvium-node v1.9.0
- packvium/packvium-wasm v1.9.0
- packvium/packvium-rust v1.9.0
- packvium/packvium-python-adapter v1.9.0
Build provenance
@packvium/engine@packvium/browser
1.8.0
- Published
- Registries checked
A result now says how far it can be from the best possible answer, and optimal means it reached that bound.
- Under the default and lowest_cost objectives a result carries optimality.lower_bound - the engine's lower bound on the score - and, where the answer is above it, gap_key, absolute_gap and relative_gap. Every engine's validate checks the bound and the gap.
- Changed: optimal is set only when the answer reaches the bound, not when the search runs out, and an effort budget names a stop: a run that ends on exactly its budget is complete. In Python and PHP time_limit_ms is no longer split across starts.
- Changed: keep_upright, stackable, must_be_on_floor and require_placement_coordinates must be booleans; "no" or 1 is refused as wrong_type instead of being read as a default or as true.
- @packvium/engine's validate answers without the compiled addon, with the same issues in the same order; ValidatorUnavailableError is deprecated and nothing throws it.
- Fixed: solvers: ["homogeneous_blocks"] alone packs under fast and balanced instead of placing nothing, and every validate reads units: null as millimetres.
Documented in
Served by
- packvium PyPI
- packvium/packvium Packagist
- @packvium/engine npm
- @packvium/browser npm
- packvium crates.io
Cut from tags
- packvium/packvium-python v1.8.0
- packvium/packvium-php v1.8.0
- packvium/packvium-node v1.8.0
- packvium/packvium-wasm v1.8.0
- packvium/packvium-rust v1.8.0
- packvium/packvium-python-adapter v1.8.0
Build provenance
@packvium/engine@packvium/browser
1.7.0
- Published
- Registries checked
The reference validator ships in every package, so a result can be checked by code that shares nothing with the engine that produced it.
- validate(request, result) returns the issues it finds - a code and a detail each, empty for a valid result - and refuses a result of the wrong shape as MalformedResult. Python, PHP, Rust and @packvium/browser run it anywhere; @packvium/engine needs its compiled addon and otherwise throws ValidatorUnavailableError.
- @packvium/engine adds scene.js: resultToScenes(request, result) returns one packvium-visualization-scene/v1 per packed container, and artifactToScene builds one from an operational artifact.
- Changed in every engine: a value outside its schema list - a rotation, an output or dimensional-weight unit, a shape_type, a ground_contact_rule, a solver name - is refused as not_allowed at its JSON Pointer. ticks as an output unit is refused, as the schema always said, and a nesting_height not below its item's height is refused as invalid_value.
- Changed: quality completes its leading blocks greedily and commits the best, so its block answer is never worse than the greedy pass. In Python and PHP a request built from objects is refused as its JSON would be.
- Fixed: the JavaScript engine reports no_eligible_container as proven, as the others do, and Rust applies incompatible_tags item against item. Breaking in @packvium/browser: a refused call throws a typed Error instead of a string, and the package needs Node 18 or later.
Documented in
Served by
- packvium PyPI
- packvium/packvium Packagist
- @packvium/engine npm
- @packvium/browser npm
- packvium crates.io
Cut from tags
- packvium/packvium-python v1.7.0
- packvium/packvium-php v1.7.0
- packvium/packvium-node v1.7.0
- packvium/packvium-wasm v1.7.0
- packvium/packvium-rust v1.7.0
- packvium/packvium-python-adapter v1.7.0
Build provenance
@packvium/engine@packvium/browser
1.6.0
- Published
- Registries checked
Boxes cut to measure, flat mailers, stacking groups and a volume-first objective, and an unpacked item names the limit that left it out.
- A container can be a box machine: made_to_measure takes a minimum size, a cut step and, optionally, a board price and weight per square metre. Each packed box is the load's extent rounded up onto that grid and priced as cut; the result reports it as achieved_dimensions.
- A container can be a flat bag: deformable_boundary {kind: flat_bag} admits a load when its length plus thickness and its width plus thickness fit the mailer.
- stacking_group and accepts_stacking_groups say which item classes may rest directly on which, and the objective maximum_volume ranks the volume left behind ahead of the number of items left behind. A result also warns when an item rests on nothing because minimum_support_ratio is 0.
- Changed in every engine: an item a fresh container would take, when none is left, reports container_inventory_exhausted, and one that overloads an axle wherever it stands reports axle_overloaded, both inferred. Code that matched no_feasible_placement or search_exhausted for these cases must match the new reason.
- Changed in the JavaScript engine: balanced and quality try eight orderings by default, as the other engines do, so answers can improve; multi_start_orders: 1 restores the 1.5 search. Fixed: effort_budget caps the whole request rather than each start, a restart keeps item priority, and quality in every engine ranks a convex_hull item by its own solid instead of its box.
Documented in
Served by
- packvium PyPI
- packvium/packvium Packagist
- @packvium/engine npm
- @packvium/browser npm
- packvium crates.io
Cut from tags
- packvium/packvium-python v1.6.0
- packvium/packvium-php v1.6.0
- packvium/packvium-node v1.6.0
- packvium/packvium-wasm v1.6.0
- packvium/packvium-rust v1.6.0
- packvium/packvium-python-adapter v1.6.0
Build provenance
@packvium/engine@packvium/browser
1.5.0
- Published
- Registries checked
A mistake in a request is refused instead of quietly ignored, and a support requirement holds on every search path.
- A configuration key the schema does not declare - profile for solver_profile, top_k for alternatives - is refused in all four engines with reason not_allowed and its JSON Pointer, such as /configuration/profile. Earlier engines ignored it and solved on defaults. An unknown objective or access direction is refused the same way, instead of as invalid_value with no field.
- Fixed: with the quality profile and a minimum_support_ratio, the block solver no longer runs. A block set on a smaller one overhangs it, so the JavaScript engine could return items below the requested ratio and Rust failed validation. Block answers now report the support each item really has, not 1.0.
- Added: Python exports its typed refusals from the package root and adds artifacts.replay_level(result); Rust adds PackError::code(), PackError::request_error() and pack_json_with. Rust's undeclared parallel key is now refused; pass ExecutionOptions instead.
- Beam search skips expansions that cannot beat the best plan so far, in all four engines, with the same results.
- Fixed in single engines: PHP refuses a number past its integer range instead of clamping it, Python's Length refuses a fractional float, and in JavaScript rebalanceWeight no longer leaves an item floating and route packing with a -x door places every item of its regression scene.
Documented in
Served by
- packvium PyPI
- packvium/packvium Packagist
- @packvium/engine npm
- @packvium/browser npm
- packvium crates.io
Cut from tags
- packvium/packvium-python v1.5.0
- packvium/packvium-php v1.5.0
- packvium/packvium-node v1.5.0
- packvium/packvium-wasm v1.5.0
- packvium/packvium-rust v1.5.0
- packvium/packvium-python-adapter v1.5.0
Build provenance
@packvium/engine@packvium/browser
1.4.0
- Published
- Registries checked
A job that has already started can be replanned: what is loaded stays put, and every change is recorded against the plan it changed.
- A request can pin items where they already are with fixed_placements: an item type, a container instance, a position and one orientation. The solve packs around them, and they count toward weight, support and top load. A fixed set that cannot hold on its own is refused before any search.
- Plan revisions record what happened on the dock - a missing item, a substituted container, a placement locked or verified - against the artifact they changed, chained by SHA-256, and carry the request the next plan solves. All four engines compute the same bytes.
- A malformed request is refused by name in every engine: a reason from a closed set of nine, the JSON Pointer of the value refused, and the same message. Python, PHP and JavaScript throw it as a subclass of the exception they threw before, so existing handlers still catch it; in Rust it is a new PackError variant, and an exhaustive match on PackError now needs a wildcard arm.
- Changed: container ids number each type from 1 in every engine. Only answers that open more than one container type change, and only in their ids.
- Fixed: values below their floor are refused instead of packed. The JavaScript engine had accepted negative lengths, weights and payloads, and quantities or limits below their minimum.
Served by
- packvium PyPI
- packvium/packvium Packagist
- @packvium/engine npm
- @packvium/browser npm
- packvium crates.io
Cut from tags
- packvium/packvium-python v1.4.0
- packvium/packvium-php v1.4.0
- packvium/packvium-node v1.4.0
- packvium/packvium-wasm v1.4.0
- packvium/packvium-rust v1.4.0
- packvium/packvium-python-adapter v1.4.0
Build provenance
@packvium/engine@packvium/browser
1.3.0
- Published
- Registries checked
A validated result leaves the engine as one document that a warehouse system can use offline.
- One operational artifact wraps the execution plan and adds exact geometry, the values a work order prints, and the request that produced it. All four engines build it, and for the same result they build the same bytes.
- It exports as canonical JSON, as CSV with 18 columns, or as a self-contained HTML work order with print styles, no scripts and no external resources.
- A solve that stopped on a time limit is marked as not guaranteed to replay, and placements are addressed by a derived reference, never by an item id a caller may reuse.
- Nothing written against 1.2.0 breaks: every golden execution plan keeps its 1.2.0 bytes. Beam search and catalog lookups do less repeated work with the same output, and the comparator sweep, rerun for this release, moved no number.
- Fixed: the published 1.2.0 PHP execution plan escaped U+2028 and U+2029, so it differed from the other engines for any text holding either character.
Served by
- packvium PyPI
- packvium/packvium Packagist
- @packvium/engine npm
- @packvium/browser npm
- packvium crates.io
Cut from tags
- packvium/packvium-python v1.3.0
- packvium/packvium-php v1.3.0
- packvium/packvium-node v1.3.0
- packvium/packvium-wasm v1.3.0
- packvium/packvium-rust v1.3.0
- packvium/packvium-python-adapter v1.3.0
Build provenance
@packvium/engine@packvium/browser
1.2.0
- Published
- Registries checked
Plans an operator can follow, and the intelligence API exported whole.
- A validated result becomes a work order in all four engines: what to lift, why each carton was chosen, and what was not packed with its proof level unsoftened. Given the same result, all four emit the same bytes.
- In Python, an operator can lock a placement and get a constrained re-solve beside the approved plan. A lock only reserves; it never forces an item into place.
- Also in Python: scenario comparison, recommendation publication, and replay against recorded shipment outcomes with a held-out slice, all exported from the package.
- Fixed in @packvium/engine: with the quality profile or a beam width above 1, 1.0.0 and 1.1.0 could report items as packed without returning their placements. Python, PHP and Rust were never affected.
- Nothing written against 1.1.0 breaks. Every schema change is additive, and it went out by tag like 1.1.0, with build provenance on both npm packages.
Documented in
Served by
- packvium PyPI
- packvium/packvium Packagist
- @packvium/engine npm
- @packvium/browser npm
- packvium crates.io
Cut from tags
- packvium/packvium-python v1.2.0
- packvium/packvium-php v1.2.0
- packvium/packvium-node v1.2.0
- packvium/packvium-wasm v1.2.0
- packvium/packvium-rust v1.2.0
- packvium/packvium-python-adapter v1.2.0
Build provenance
@packvium/engine@packvium/browser
1.1.0
- Published
- Registries checked
The first fully tag-driven release, on a contract already frozen at 1.0.
- The public API, frozen at 1.0.0 — schemas, numeric policy and validation rules — carries forward unchanged; incompatible changes still require 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
- packvium PyPI
- packvium/packvium Packagist
- @packvium/engine npm
- @packvium/browser npm
- packvium crates.io
Cut from tags
- packvium/packvium-python v1.1.0
- packvium/packvium-php v1.1.0
- packvium/packvium-node v1.1.0
- packvium/packvium-wasm v1.1.0
- packvium/packvium-rust v1.1.0
- packvium/packvium-python-adapter v1.1.0
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
- packvium PyPI
- packvium/packvium Packagist
- @packvium/engine npm
- @packvium/browser npm
- packvium crates.io
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.