packager.default

To package build-time dependencies for offline execution, you can resolve and bundle them into layered artifacts. This process preserves runtime metadata and validation requirements to ensure deterministic builds across network-isolated environments.

Yes, you can bundle Python, Node.js, and Go dependencies into artifact layers. The packager resolves dependencies across these common ecosystems and packages them for portable, offline runtimes.

The best way to ensure reproducible builds across isolated CI environments is to package build-time dependencies into layered artifacts. Attaching runtime metadata and validation requirements guarantees deterministic execution without network access.

Dependencies are captured using capture_paths when bundling artifacts for offline runtimes. This method preserves the original artifact kind while assembling the necessary runtime layers for network-isolated deployment.

You need to attach runtime metadata to packaged dependency layers to enforce validation requirements and ensure deterministic builds. This metadata guarantees the bundled layers execute correctly in network-isolated environments.

Yes, layering build-time dependencies works for portable agent runtimes. Bundling dependencies into layered artifacts provides the network-isolated, reproducible execution environment required by portable agents.