fix(oci): bump rust-builder-glibc to v1.0.2 and guard dx/dioxus match #53
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/dx-dioxus-guard-LINKS-19"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Fixes the dx/dioxus version mismatch surfaced in OCI build run #136 (LINKS-19). The
rust-builder-glibcbase image pinned dx 0.7.7, but this repo resolvesdioxusto 0.7.9 inCargo.lock, sodx build --releaseprinteddx and dioxus versions are incompatible!and continued, risking a silently broken WASM client bundle.Changes
oci-build/DockerfileFROM tagv1.0.1-rust1.94-trixie->v1.0.2-rust1.94-trixie. v1.0.2 ships dx 0.7.9, published by the companionniceguyit/oci-imageschange (fix(rust-builder-glibc): bump dioxus-cli to 0.7.9).dx --versionand thedioxusversion fromCargo.lockandexit 1s on a mismatch. A future dx/dioxus drift now fails fast instead of warning and continuing. The check is exact-patch: dx 0.7.7 vs dioxus 0.7.9 share the 0.7 minor yet dx still flags them incompatible, so a minor-only compare would miss it.Merge ordering (IMPORTANT)
Do NOT merge this until the
oci-imagesPR is merged AND its CI has publishedghcr.io/niceguyit/rust-builder-glibc:v1.0.2-rust1.94-trixie. Merging earlier makes the rusty-links build fail: the FROM tag will not resolve, and once it does, the guard correctly rejects any base image still on dx 0.7.7.Acceptance criteria
oci-build/Dockerfile:3FROM bumped to the dx-0.7.9 tag (AC2).niceguyit/oci-images(GitHub); branchfix/dioxus-cli-0.7.9-LINKS-19is committed locally, pending push by a maintainer with GitHub access.dx buildno longer warns) verified by the first main build after both merge.Refs LINKS-19.