Releases

How versions and images move from develop to a tagged release. This guide follows version 3.1.7 (03acdf712c).

For upgrading a deployment, see Upgrades.

Branches and versions

• The contribution guide targets develop as the base for feat/, fix/, and docs/ branches; confirm the base with maintainers if your checkout differs.
• Root package.json declares the product version (3.1.7 in the checked revision) with release-it (pnpm release).
• CI builds per-service images (ci-api-*.yml, ci-core-ui.yml, ci-service-*.yml, ci-apps-*.yml) tagging erxes/erxes-next-<service>:latest plus date-SHA tags. release.yml promotes tested :latest images to :$VERSION.

A product version does not prove every image has a matching tag. Record the image set you tested together before deploying; see Upgrades.

Before a release

1. Land changes on the agreed base with focused commits and updated tests.
2. Update documentation when user-facing behavior changes.
3. Verify pnpm nx affected -t lint,build,test and the staged deployment from Database Migrations.
4. Maintainers manage merge and release decisions; do not promise a review deadline.

Source references

• Release workflow.
• Contribution guide.