Skip to content

v1.19.3 — Operator guidance and deployment evidence

Choose a tag to compare

@github-actions github-actions released this 18 Oct 14:55
Immutable release. Only release title and notes can be modified.
d0c2cba

v1.19.3 — Operator guidance and deployment evidence

This patch corrects operator instructions, strengthens deployment-evidence validation and repairs French navigation. The primary deployment remains the owner-reported 17 October Manager; the separate 10 October ENS-connected instance retains its historical scope. Software versions advance together to 1.19.3; package dependency resolutions remain unchanged.

The previous immutable stable release is v1.19.2, source 193d59b96e2e4d3074186f1fc6f90793fc5a56b6, tree f17fd5a933cdb626d3c046eb0ceaba0698e820f6. Its source, assets, qualification and preparation guides retain their original bytes and scope. Final source identity, qualification and publication evidence for this patch are supplied by its external QUALIFICATION.json, release metadata and publication workflow. See the dated preparation snapshot.

Operator instructions

Current deployment guidance now reflects atomic explicit-governor creation: governed contracts are created with the selected governor, without a mandatory later ownership acceptance or a deployer administration window. Creating an ENS helper leaves its Manager binding unset and configuration unlocked; its ENS, wrapper, resolver and root constructor settings remain explicit. Binding and locking require a separate reviewed governor plan. The Hardhat guide describes the supported local hidden-terminal key route and current preparation status.

ENS verification recovery uses all six recorded constructor arguments, including the governor. The optional metadata-router guide uses the current v2 direct-creation configuration with an explicit creator and independent governor. Executable documentation checks validate these recipes against the frozen tools while preserving authentic historical recovery inputs.

The documented qualified Manager runtime is 24,477 bytes, leaving 99 bytes below the EIP-170 limit. This is a correction to the description of the qualified artifact, not a bytecode change or new deployment receipt. Existing contracts must be inspected and operated with their own original source and journals.

Evidence and website checks

Future primary deployment records must carry matching reviewed evidence and guides; a new record cannot inherit the older fixed evidence-source link. Owner and pending-owner states must support the fixed governor label. The embedded document guard rejects raw opening-script tokens that can disrupt HTML script parsing, with a regression covering a coordinated README and embedded-bundle modification. French footer navigation retains the selected language, and workflow pages carry canonical and alternate-language links.

The 17 October record still identifies Manager 0x3a9B3A0712e066de4265404Fa5ff4171fE29a3F8, its original deployed source and nine reported finalized creations: six Exact Matches and three retained Similar Matches. Its authority snapshot reports paused intake and unlocked identity configuration. These dated owner-reported observations are not live state or independent paid-operation qualification, and establish no new ENS helper attachment. Neither this panel nor the separate 10 October instance selects a transaction target or migrates obligations.

Preserved source boundaries

The immutable integrated baseline remains commit 8815ed3181778664595f951befd672afbd7a9352, tree 913e49d65263bc53026916f7fc3b4cbfb93549f8. This patch changes guidance, presentation and evidence guards, with no Solidity, compiler behavior, dependency-resolution or transaction-logic changes. Inherited capabilities include explicit governor selection, source-bound creator profiles, finite deployment inventories, recoverable journals and bounded read-only preflight retry. The pinned Solidity 0.8.37 optimizer mitigation, via IR, 40 runs and Shanghai target retain their existing source binding. See the integrated candidate record.

The Builder remains separately pinned to commit ab516fbd32fd7cf1a9620fd630947fee1455fca2, tree b011643b56115c5baa39ca796cbf0a944c152eda, version 1.17.2. Its selected source, retained context and editable-source inventory must agree. A release-wrapper commit must not replace that Builder identity.

New fork and static-analysis comparison inputs preserve previous observations and finding dispositions, changing only applicable software-version source hashes. They are expectations, not new execution receipts. Publication requires all eight fresh exact-main-source workflows, reproducible assets, clean extraction, uploaded-byte verification and source-bound attestations. This release performs no on-chain action and establishes no activation, independent audit, live-provider qualification or live paid-work readiness.