Bump Version and Prepare a Release

Get Started
Functionality
Learning
Extension
Dev Tooling
APIs
Releases

How-to Guide

Author:

Fluent Commerce

Changed on:

31 Mar 2026

Key Points

[Warning: empty required content area]

Prerequisites

Getting Started with the Fluent CLI

Getting started with the Fluent Builder MCP server

Generate GraphQL queries using the Builder MCP Server

Steps

Check Current Version

`What version is the my-extensions module?`

`/fluent-build` reads the version from `module.json`, `pom.xml` (parent + child), and CHANGELOG. Reports any inconsistencies (e.g., POM says 1.3.0 but module.json says 1.2.9).

Bump the Version

`Bump my-extensions to 1.4.0`

Updates ALL version references in sync: - `plugins/pom.xml` (parent version) - `plugins/rules/<module>/pom.xml` (module + parent version) - `resources/module.json` (version field) - `CHANGELOG.md` (moves [Unreleased] entries to [1.4.0])

Build

`Build it`

`/fluent-build` runs `mvn clean install`, packages the ZIP, verifies the output artifact.

Pre-Deploy Gates

`Run pre-deploy checks`

35+ quality gates across 9 phases. If all pass → READY. If any critical gate fails → BLOCKED with specific fix instructions.

Deploy

`Deploy to MY_RETAILER`

Module install + post-deploy verification.

Common Issues

Version mismatch — `module.json` says 1.4.0 but `pom.xml` still says 1.3.0. Run `/fluent-build` to sync all version references.
Build fails after version bump — stale `dist/` artifacts from the old version. Clean build (`mvn clean install`) resolves this.
Pre-deploy gate fails on "module already deployed at same version" — bump the version again or use a `-SNAPSHOT` suffix for testing.

Bump Version and Prepare a Release - Fluent AI Skills