How we release Dagger

At Dagger, CI/CD is a crucial aspect that they think about extensively. They release as often as necessary in small batches and prioritize fixing issues within days. Larger features are released behind an experimental environment variable flag to gather real-world feedback from users. Five different artifacts - Dagger Engine, CLI, Go SDK, Python SDK, and Node.js SDK - are released, all originating from the monorepo github.com/dagger/dagger. The release process involves GitHub Actions workflows that trigger on specific git tags, publishing artifacts to various registries like registry.dagger.io. Documentation is a cross-cutting artifact closely coupled with the other releases, built on Netlify for two separate websites. Dagger uses its own SDKs to publish itself, showcasing "first-class dogfooding." To improve their release process, they are considering announcing new SDK releases in Discord and configuring a release bot, automatically publishing documentation when new SDK releases go out, and improving their release notes to be friendlier and more readable.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.