Introduction

Rush Delivery is a provider-adaptable Dagger module for Rush monorepos. The framework assumes Rush is the project graph and uses .dagger/ metadata as the extension surface for validation, packaging, deployment, caches, and toolchains.

Guides

• Quick Start: recommended ways to run Rush Delivery from GitHub Actions, CI scripts, and local working trees.
• GitHub Action usage: GitHub CI wrapper for validation, deploy release workflows, and npm package release workflows.
• Public Dagger API: callable functions and when to use them.
• Entrypoints reference: every callable Dagger function and separate-use workflow.
• Workflow guide: local and CI workflow shapes.
• Metadata contracts: files under .dagger/ that define target behavior.
• Provider adapters: source, registry, cache, and CI-provider boundaries.
• Development: maintainer checks, website build notes, and generated documentation inputs.
• AI architecture: high-level design map for future coding agents.
• AI conventions: contribution rules and invariants.

Source Of Truth

The schemas under ../schemas are the field-level metadata contract. These docs explain intent and usage; schemas define file shape.

Published schemas are available from the documentation site:

• https://bootstraplaboratory.github.io/rush-delivery/schemas/<schema>.schema.json
• https://bootstraplaboratory.github.io/rush-delivery/schemas/v0.7.0/<schema>.schema.json

Use exact versioned schema URLs in project metadata editor hints so older projects keep the schema contract they were written against. The root /schemas/ URLs point at the current release line.

Package Release Reference

The package release docs use BootstrapLaboratory/labkit as a real npm package publishing reference. LabKit publishes public npm packages with Rush Delivery v0.7.0, Rush change files, .dagger/release/npm.yaml, and the same package release contract that can run standalone or as part of workflow.