Repository navigation
v1.19.2 — Current deployment records and consistent interfaces
v1.19.2 — Current deployment records and consistent interfaces
This patch corrects stale deployment presentation across the English/French website, downloadable USDC console and operator guidance. The latest reported 17 October Manager is the primary read-only record, with its nine contract/code and creation-transaction links and dated authority snapshot. The separate 10 October ENS-connected instance remains accessible as history. Software versions advance together to 1.19.2; package dependency resolutions remain unchanged.
The previous immutable stable release is v1.19.1, source d5d4ad93f00a3dfe6439b0f32edb1a2fcf70e0c2, tree 215c3d39eaf87424dbbe8097a8b0b1f0723bd555. 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.
Deployment presentation
The 17 October record identifies Manager 0x3a9B3A0712e066de4265404Fa5ff4171fE29a3F8 and the original deployed source. Its reported nine finalized creations comprise six Exact Matches and three retained Similar Matches. The authority snapshot reports paused intake and unlocked identity configuration. These are dated owner-reported observations, not live state or independent paid-operation qualification. The record establishes no new ENS helper attachment. Displaying it does not select a transaction target.
The 10 October instance, its helper and namespace remain separate. Its jobs, credits and claims remain on that original manager; its ENS wiring must not be copied to the newer deployment by inference.
Preserved source boundaries
The immutable integrated baseline remains commit 8815ed3181778664595f951befd672afbd7a9352, tree 913e49d65263bc53026916f7fc3b4cbfb93549f8. This patch changes presentation and release metadata, with no Solidity, compiler behavior, dependency-resolution or deployment-tool 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.