route-proxy: the server container resolves its own built artifact #66

Merged
jschoubben merged 1 commits from fix/route-proxy-server-uses-its-real-artifact into main 2026-09-25 16:09:19 +00:00
Owner

Was still pinned to the scaffold's placeholder digest (mesh-route-proxy@sha256:0000...0000) even after the build+context work landed — never caught because nothing had assigned route-proxy before tonight. artifact: server, matching trust's own reference a few lines up and every other built module in the catalogue.

Was still pinned to the scaffold's placeholder digest (`mesh-route-proxy@sha256:0000...0000`) even after the build+context work landed — never caught because nothing had assigned route-proxy before tonight. `artifact: server`, matching `trust`'s own reference a few lines up and every other built module in the catalogue.
jschoubben added 1 commit 2026-09-25 16:09:15 +00:00
Was still pinned to the scaffold's placeholder digest (mesh-route-
proxy@sha256:0000...0000) even after the build+context work landed —
never caught because nothing had assigned route-proxy before tonight.
artifact: server, matching trust's own reference a few lines up and
every other built module in the catalogue.
jschoubben merged commit d243b56942 into main 2026-09-25 16:09:19 +00:00
jschoubben deleted branch fix/route-proxy-server-uses-its-real-artifact 2026-09-25 16:09:19 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#66