Bryan Helmkamp 7c73f7ac02 fix(server): inline dockerfiles defined in the [environments.*] catalog ... The manifest bundler collects Dockerfile path references from both the named-environment catalog and [run.environment], but the server-side resolver only inlined [run.environment.image]. A Dockerfile declared under [environments.<slug>.image] therefore reached the Daytona provider as an un-inlined Path and tripped its guard ("dockerfile path should have been resolved to inline content before sandbox creation"), so no run could use a catalog-defined Dockerfile environment. Walk layer.environments alongside run.environment when resolving manifest dockerfiles, mirroring the bundler. Add a regression test proving a catalog dockerfile path is inlined. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-05-29 11:38:10 -04:00
..
crates	fix(server): inline dockerfiles defined in the [environments.*] catalog	2026-05-29 11:38:10 -04:00
packages/fabro-api-client	refactor: Remove inbound IP allowlisting (#443)	2026-05-27 22:29:08 -04:00