A Source-Driven Direction for dx Mate

When we first introduced dx Mate, we described a conversation-first, visual-reactive way to run Salesforce deployments. That foundation hasn’t changed — but the model underneath it has sharpened.

The change bundle

dx Mate is now built around a single first-class idea: the change bundle. A bundle is a feature or bugfix, assembled from a git branch or from an org’s changes, that you promote through your pipeline as one unit. The platform always knows which bundles are at which stage — so “where’s my change?” is a question you can simply ask.

Git is the source of truth

Every bundle is backed by a real git ref. Connect an existing repository, or let dx Mate initialize one straight from your production org. Early stages move source; release stages move immutable, versioned unlocked packages. Promoting to production merges your bundle’s branch to main — git advances with your pipeline, not beside it.

Scratch orgs and sandboxes, in one pipeline

A pipeline stage can be backed by a static sandbox or by a DevHub-generated scratch org, provisioned on demand and source-pushed from the bundle’s branch. You get ephemeral, reproducible environments where you want them and stable ones where you need them — described in plain language, the same way as everything else.

What this means for you

• Assemble a feature into a bundle from a branch or an org
• Promote it stage to stage across scratch orgs and sandboxes
• Ask where any change is, what’s blocking a stage, or what’s in QA that isn’t in production
• Ship releases as immutable package versions

We’re still in active development. Follow along here for deeper dives as each phase lands.