fix(oci): pin dioxus to 0.7.7 and restore FROM to v1.0.1 #55

Merged

nrupard merged 1 commit from fix/pin-dioxus-0.7.7-LINKS-23 into main

2026-06-09 15:55:58 +02:00

nrupard commented

2026-06-09 15:52:37 +02:00

Owner

Problem

The build-oci-image.yml workflow on main fails at the very first build step (run #148, commit 4ab506b3). Dockerfile line 3 pinned the builder base to ghcr.io/niceguyit/rust-builder-glibc:v1.0.2-rust1.94-trixie, but that tag was never published to GHCR (not found / failed to resolve source metadata). The v1.0.2 base bump was rejected; the supported toolchain is the existing v1.0.1 image, which ships dx (dioxus-cli) 0.7.7.

Fix

Restore the builder FROM to the existing v1.0.1-rust1.94-trixie tag and align the dioxus crate to the toolchain it pins:

oci-build/Dockerfile: FROM v1.0.2-rust1.94-trixie -> v1.0.1-rust1.94-trixie.
Cargo.toml: pin dioxus and dioxus-web to exact =0.7.7 so the facade cannot drift back up to 0.7.9 (which dx 0.7.7 reports as incompatible and the LINKS-19 guard rejects).
Cargo.lock: regenerated so the dioxus / dioxus-web facades resolve to 0.7.7. The caret-compatible monorepo sub-crates (dioxus-core, dioxus-html, etc.) remain at 0.7.9; dx 0.7.7 builds that set without issue (the LINKS-19 "incompatible" check only inspects the top-level dioxus facade, which is now 0.7.7).

Verification

Full docker build -f oci-build/Dockerfile . run locally to completion:

FROM v1.0.1-rust1.94-trixie resolves (no 404).
LINKS-19 guard passes: dx=0.7.7 dioxus=0.7.7.
wasm-bindgen 0.2.111 and wasm-opt both run; no wasm-opt failed.
Client bundle is the optimized 1.83 MB, not the 3.4 MB unoptimized fallback (LINKS-20 path stays healthy).
Build exits 0; runtime image assembles.

Closes the run #148 failure once merged.

#LINKS-23

## Problem The `build-oci-image.yml` workflow on `main` fails at the very first build step (run #148, commit `4ab506b3`). Dockerfile line 3 pinned the builder base to `ghcr.io/niceguyit/rust-builder-glibc:v1.0.2-rust1.94-trixie`, but that tag was never published to GHCR (`not found` / failed to resolve source metadata). The v1.0.2 base bump was rejected; the supported toolchain is the existing `v1.0.1` image, which ships `dx` (dioxus-cli) 0.7.7. ## Fix Restore the builder FROM to the existing `v1.0.1-rust1.94-trixie` tag and align the dioxus crate to the toolchain it pins: - `oci-build/Dockerfile`: FROM `v1.0.2-rust1.94-trixie` -> `v1.0.1-rust1.94-trixie`. - `Cargo.toml`: pin `dioxus` and `dioxus-web` to exact `=0.7.7` so the facade cannot drift back up to 0.7.9 (which dx 0.7.7 reports as incompatible and the LINKS-19 guard rejects). - `Cargo.lock`: regenerated so the `dioxus` / `dioxus-web` facades resolve to 0.7.7. The caret-compatible monorepo sub-crates (dioxus-core, dioxus-html, etc.) remain at 0.7.9; dx 0.7.7 builds that set without issue (the LINKS-19 "incompatible" check only inspects the top-level `dioxus` facade, which is now 0.7.7). ## Verification Full `docker build -f oci-build/Dockerfile .` run locally to completion: - FROM `v1.0.1-rust1.94-trixie` resolves (no 404). - LINKS-19 guard passes: `dx=0.7.7 dioxus=0.7.7`. - wasm-bindgen 0.2.111 and wasm-opt both run; no `wasm-opt failed`. - Client bundle is the optimized 1.83 MB, not the 3.4 MB unoptimized fallback (LINKS-20 path stays healthy). - Build exits 0; runtime image assembles. Closes the run #148 failure once merged. #LINKS-23

nrupard added 1 commit

2026-06-09 15:52:37 +02:00

fix(oci): pin dioxus to 0.7.7 and restore FROM to v1.0.1

Check / clippy + fmt + tests (pull_request) Successful in 25s

Details

Create release / Create release from merged PR (pull_request) Has been skipped

Details

f16083ff11

The OCI build off main failed at FROM resolve because rust-builder-glibc:v1.0.2-rust1.94-trixie was never published to GHCR (the v1.0.2 base bump was rejected; v1.0.1 with dx 0.7.7 is the supported toolchain). Point the builder FROM back at the existing v1.0.1-rust1.94-trixie tag.

To satisfy the LINKS-19 dx/dioxus guard against dx 0.7.7, pin the dioxus and dioxus-web crates to an exact =0.7.7 and regenerate Cargo.lock so the dioxus facade resolves to 0.7.7 (caret-compatible monorepo sub-crates remain at 0.7.9, which dx 0.7.7 builds without issue). Verified end-to-end with a full docker build of oci-build/Dockerfile: FROM v1.0.1 resolves, the guard passes (dx=0.7.7 dioxus=0.7.7), wasm-bindgen and wasm-opt complete, and the client bundle is the optimized 1.83 MB (not the 3.4 MB unoptimized fallback).

#LINKS-23

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>