Deploy fixed releases from Git tags
TLDR
Choose a branch or a release tag as the production source in Mage Pro, then deploy an exact version your team can identify and reproduce.
Deploy the version your team approved
Production should run a version you can identify and reproduce. In Mage Pro, choose a branch or a release tag as the production source for a deployment, then select the exact version you want to ship.
Choose the source that fits your release process
- Use a branch for a moving production source. Mage shows the commits available from the selected branch so your team can deploy the version it needs.
- Use a tag for a fixed release version. Select an available release tag when production should point to a named Git reference instead of a moving branch.
- Keep the decision visible. The repository, source type, and selected version stay together in the deployment setup.
Make production releases easier to trace
A release tag gives operators and reviewers a shared name for the code being promoted. That makes it easier to verify an approved release, reproduce the deployed version, and communicate what production is running without relying on a moving branch alone.
Use branches and tags deliberately
Branches remain useful for development and continuous delivery workflows. Tags are a better fit when your release process requires a fixed version boundary. Mage Pro supports both so the deployment source can match the way your team ships.
