Repository navigation
type: component-release-note
status: draft
component: compact-js
version: 3.0.2
component_class: library/SDK
template_blob_sha: f20b0b2a13f82201bb2ce3e2f60523c85bf7c751
template_commit_sha: 3cf24faefda49b1daa58e892ec641b6ca8a13b9c
generated: 2026-11-17
generator: component-rn-draft v1.4.2
tested_with_status: build-pins
compact-js 3.0.2
Metadata
- Release type: patch
Semver delta 3.0.1 to 3.0.2, taken fromversion.jsonand the three package manifests (commit 9ca8ed2). - Date: 2026-11-17 (owner-confirmed 2026-11-17)
- Sister-line note: —
- Environment: not environment-scoped — the packages carry both the ledger 8 (
/v8) and ledger 9 (/v9) eras, and a consumer selects one at import - Released artifact(s): three npm packages at 3.0.2 — see Artifacts
- Component class: library/SDK (drives which operator fields apply; see Deployment information below)
- Upgrade scope: N/A — library
- Reset required: N/A — library
- Governance action required: N/A — library
High-level summary
compact-js 3.0.2 is a dependency-promotion patch. The ledger 9 era is built against the final
@midnightntwrk/ledger-v9 1.0.2 and @midnightntwrk/onchain-runtime-v4 4.0.2 instead of the
release candidates 3.0.1 was built against, and the published manifests now declare those final
versions as their floor. No compact-js source file changed, and the ledger 8 era is untouched.
Audience
These notes are written for:
- Developers building DApps on the
@midnight-ntwrk/compact-jspackages. - Developers who pin compact-js transitively through a consuming SDK and care which ledger 9
binding resolves in their install tree. - Shielded Technologies engineering teams maintaining consuming SDKs.
Dependencies
- Requires
@midnightntwrk/ledger-v9>= 1.0.2 for the ledger 9 era; the manifest declares
^1.0.2. - Requires
@midnightntwrk/onchain-runtime-v4>= 4.0.2 - The compact runtime pin is unchanged at the exact version 0.21.0, so the compactc 0.36
requirement introduced in 3.0.0 carries over unaltered. - The ledger 8 era stays on
@midnightntwrk/ledger-v88.1.3 over compact runtime 0.16.0.
Downstream impact (cascading effects). A consuming SDK or DApp that takes compact-js 3.0.2
resolves the final ledger 9 binding and on-chain runtime rather than a release candidate, which
is the pair compact-js itself was built and tested against at this version (package.json,
yarn.lock at commit 9ca8ed2). @midnight-ntwrk/compact-runtime 0.21.0 declares ^4.0.0-rc.3 for the
on-chain runtime; ^4.0.2 intersects it at 4.0.2 and above, so a fresh install still resolves a
single copy (package.json). Consumers that carry their own resolutions or overrides entry
pinning @midnightntwrk/onchain-runtime-v4 to 4.0.2-rc.0 should drop it. Nothing a consumer
depends on differs between the release candidates and the finals: the Ledger 9.1.0.2 release note
describes 9.1.0.2 as a post-QA promotion of 9.1.0.2-rc.0 whose only post-candidate movement was in
the proof server, and the component owner confirms the bindings carry no consumer-visible change
(owner-confirmed 2026-11-17).
Tested-with versions
Read from the package manifests and the lockfile at this revision: these are build pins — not QA-verified.
| Component | Tested-with version |
|---|---|
compact runtime (@midnight-ntwrk/compact-runtime) |
0.21.0 (package.json) |
| compact toolchain/compiler (compactc) | 0.36.0 (3.0.0 release body; the runtime pin it was read against is unchanged) |
ledger 9 bindings (@midnightntwrk/ledger-v9) |
1.0.2 (package.json) |
ledger 8 bindings (@midnightntwrk/ledger-v8) |
8.1.3 (package.json) |
on-chain runtime (@midnightntwrk/onchain-runtime-v4) |
4.0.2 (package.json) |
compact runtime, ledger 8 era (@midnight-ntwrk/compact-runtime) |
0.16.0 (package.json) |
The ledger rows name npm binding packages, which version independently of the ledger component
release line: @midnightntwrk/ledger-v9 1.0.2 is a binding version, not a ledger 9.1.0.x version.
Deployment information
- Upgrade scope: N/A — library
- Reset required: N/A — library
- Governance action required: N/A — library
- Downtime / coordination: N/A — library
Artifacts
@midnight-ntwrk/compact-js@3.0.2— core execution environment@midnight-ntwrk/compact-js-node@3.0.2— Node.js implementations of the service types@midnight-ntwrk/compact-js-command@3.0.2— CLI for executing compiled contracts
What changed
- Built the ledger 9 era against the final 1.0.2 bindings (PR #54) —
@midnightntwrk/ledger-v9
1.0.2 and@midnightntwrk/onchain-runtime-v44.0.2, replacing the 1.0.2-rc.0 and 4.0.2-rc.0
release candidates 3.0.1 resolved. - Raised the declared dependency floors in the published manifests (commit 9ca8ed2) from
^1.0.2-rc.0and^4.0.0-rc.3to^1.0.2and^4.0.2. - Changed no source file (commit 9ca8ed2): the release touches the package manifests, the
lockfile andversion.jsononly.
New features
None.
New features requiring configuration updates
None.
Improvements
Published dependency floors name the versions the release was built against
Description: per package.json, the manifests shipped with 3.0.1 declared
@midnightntwrk/ledger-v9 ^1.0.2-rc.0 and @midnightntwrk/onchain-runtime-v4 ^4.0.0-rc.3,
while the monorepo's resolutions entry built and tested that release against 4.0.2-rc.0 — so the
versions a consumer resolved were not the versions the release was verified on. In 3.0.2 the
declared floors, the lockfile and the resolutions entry all name the same final versions, 1.0.2
and 4.0.2 (commit 9ca8ed2).
Deprecations
None.
Breaking changes
None.
Known issues
compact-js and compact runtime declare different on-chain runtime ranges
Description: per compact-js issue #42,
@midnight-ntwrk/compact-js declares ^4.0.2 for @midnightntwrk/onchain-runtime-v4 while its
own dependency @midnight-ntwrk/compact-runtime 0.21.0 declares ^4.0.0-rc.3. The two ranges
intersect at 4.0.2 and above, so a fresh install today resolves one copy; the ranges are still
not written as one, and two resolved copies reject each other's WASM objects.
Workaround (if any): pin @midnightntwrk/onchain-runtime-v4 to a single version through the
consuming project's resolutions or overrides entry if an install tree does resolve two copies.
CompiledContract context fails across identical package copies
Description: per compact-js issue #28,
when two identical copies of a compiled contract package are resolved in one process, building a
contract context fails with a raw constructor TypeError.
Workaround (if any): deduplicate the contract package so a single copy is resolved.
A valid null --input-ps is rejected
Description: per compact-js issue #30,
the CLI's circuit command rejects a valid null --input-ps, so a contract whose initial private
state is null cannot be run from the CLI.
Workaround (if any): give the contract a non-null initial private state.
Links and references
- QA test coverage / test evidence: qa/tests/evidence/3.0.2/README.md (on
main; added after the release, so not in the tag) - PRs: compact-js PR #54
- Engineering docs: Ledger 9.1.0.2 release note
- SDK docs:
@midnight-ntwrk/compact-json npm - Known issues board: compact-js issues
- Related component releases: Ledger 9.1.0.2 and Proof Server 9.0.2
Fixed defect list
No compact-js defect is recorded as fixed in 3.0.2. The release moves dependency pins only, and
the ledger-side fixes carried by the 1.0.2 bindings reached consumers in 3.0.1, which already
resolved the 1.0.2-rc.0 candidate.