Lines Matching full:version

9 - Centralized version management
43 ### 2. Update Version
45 Use the automated version update system:
48 # Update to new version (use semantic versioning)
49 make version VERSION=x.y.z
52 **Version numbering guidelines:**
54 - **Patch version** (x.y.Z): Bug fixes, security patches, minor improvements
55 - **Minor version** (x.Y.z): New features, backward-compatible changes
56 - **Major version** (X.y.z): Breaking changes, major refactoring
61 make version VERSION=1.0.1  # Bug fix release
62 make version VERSION=1.1.0  # Feature release
63 make version VERSION=2.0.0  # Major release with breaking changes
66 **Note:** The current version is 1.0.0, which represents the initial stable release.
70 - Update `version.php` with new version and current date
71 - Update `plugin.info.txt` with version information
72 - Validate the new version format
77 After version update, manually update release documentation:
111 - Correct version references
119 make release VERSION=x.y.z
126 3. Update version information
142 git commit -m "Release version x.y.z"
205 make version VERSION=x.y.z  # Update version in all files
207 make release VERSION=x.y.z  # Complete release workflow
213 make status    # Show current version and git status
217 ## Version Management
219 ### Centralized Version Control
221 The plugin uses centralized version management through `version.php`:
225     'version' => 'x.y.z',
236 The `build/update-version.php` script automatically:
238 - Updates version across all relevant files
240 - Validates semantic version format
306 **Version update issues:**
309 # Manually check version.php format
310 php -r "var_dump(include 'version.php');"
330 4. **Tag releases**: Use `git tag vx.y.z` for version tracking
338 - [ ] Version updated (`make version VERSION=x.y.z`)