1

AUTO-BUMP

Jonathan Miller edited this page 2026-06-06 22:59:24 +00:00

Wiki / features / AUTO-BUMP.-

Table of Contents

• Auto Version Bump
• How It Works
• Skip Conditions
• Version Bump Sequence
• Files Updated

Auto Version Bump

Every push to dev triggers an automatic patch version bump via auto-bump.yml.

How It Works

1. version_bump.php increments the patch segment (ZZ+1)
2. version_set_platform.php propagates to all platform files
3. version_check.php --fix ensures consistency
4. Commits with [skip ci] to avoid retriggering

Skip Conditions

• [skip ci] in commit message
• [skip bump] in commit message

Version Bump Sequence

Trigger	Bump Type	Example
Push to dev	Patch (ZZ+1)	09.02.00 -> 09.02.01
Pre-release (alpha/beta/rc)	None (already bumped)	uses current
PR merge to main (stable)	Minor (YY+1)	09.02.01 -> 09.03.00

Files Updated

version_bump.php writes to all version sources:

• .mokogitea/manifest.xml
• README.md
• Joomla XML manifests
• Dolibarr mod*.class.php
• composer.json
• package.json (Node.js)
• pyproject.toml (Python)

Pages

• features
  • AUTO-BUMP
  • UPDATE-SERVER
  • Update-Server-Migration-Protocol
• operations
  • DEPLOY-SCRIPTS
  • DEPLOY_SCRIPTS
• reference
  • BULK-OPERATIONS
  • RUNNERS
  • VALIDATION
• workflows-release-system
• workflows-renovate
• workflows-reusable-workflows
• workflows-rs-deployment
• workflows-secret-scanning
• workflows-shared-workflows
• workflows-standards-compliance
• workflows-static-analysis
• workflows-sub-issue-management
• workflows-update-server
• workflows-workflow-architecture
• workflows
  • Composer-Publishing