Rush Delivery v0.9.1 is the production compatibility patch for the v0.9 deployment-environment release.
What this fixes
- The bounded local-copy GitHub Action now transports generated Dagger Shell through an owner-only script file, avoiding the quoted-input assembly failure found by the immutable v0.9.0 exact-tag smoke.
- Host env files, runtime-file bundles, and Docker sockets are converted to typed Dagger Shell objects before the module call, so runner-temporary paths keep their intended host meaning.
- The legacy Action path, remote module path, Git source mode, and the existing Docker-socket default are preserved.
Upgrade and compatibility
Existing filesystem-only, archive, npm, provider-off, static-provider, and default Node-toolchain projects do not need new OCI configuration. OCI application-image publication remains opt-in. Projects using the GitHub Action should replace @v0.9.0 with @v0.9.1; no .dagger metadata changes are required solely for this patch.
The narrow v0.9 local-copy exclusion migration remains unchanged: repositories that intentionally transfer a default-excluded dependency/cache path must re-include it in .dagger/source-import.ignore or temporarily select source-import-policy: legacy.
- v0.9.1 upgrade guide
- GitHub Action guide
- OCI application-image production guide
- OCI application-image tutorial
- Troubleshooting and recovery
Verification
The exact release commit db35bb8eefef173aa052b1264b973bdb0794912d passed the clean 447-test/typecheck self-check, all eight Action/module/launcher consumer-smoke jobs, live GHCR publication/signing/evidence/cleanup, provider-backed Rush toolchain caching, the eight-scenario v0.8.1 compatibility matrix, and both documentation-site builds.
Bundled launcher asset SHA-256:
35e60214455a84ee27078a0e71481565b1a6d8aab53ba90d511cf0d5970afc27 rush-delivery-local
The v0.9.0 tag and release remain immutable historical artifacts; use v0.9.1 for bounded GitHub Action runs.