version_assist 1.3.4
version_assist: ^1.3.4 copied to clipboard
A comprehensive CLI tool for managing version numbers in Flutter/Dart projects, supporting semantic versioning, build numbers, version control integration, and documentation updates.
Changelog #
All notable changes to this project will be documented in this file.
1.3.4 #
Changed #
- Improved command reusability by adding
runWith
method to CommitCommand - Refactored auto-commit functionality to use proper command parameters
- Fixed null safety issues in command parameter handling
1.3.3 #
Fixed #
- Fixed commit command to preserve previously staged files instead of automatically staging all files
1.3.1 #
Fixed #
- Fixed null safety issue in commit command when using
--auto-commit
flag - Improved git operations to properly stage and commit all relevant files during version bumps
1.3.0 #
Added #
-
New
set
command to manually set version numbers- Allows setting specific version numbers (e.g.,
version_assist set --version 2.0.0
) - Supports both formats: with and without build numbers
- Includes dry-run mode to preview changes
- Compatible with --auto-commit flag for version control
- Validates version format to ensure compliance
- Allows setting specific version numbers (e.g.,
-
New
badge
command to update version badges in README.md- Command automatically syncs version badge with pubspec.yaml version
- Supports dry-run mode to preview changes
- Configurable file paths for both pubspec.yaml and README.md
- Comprehensive error handling for missing files and invalid versions
-
New
commit
command for version control operations- Creates commits and tags for versions independently
- Supports dry-run mode to preview changes
- Configurable pubspec.yaml path
- Integrated with existing --auto-commit functionality
Changed #
-
BREAKING: Version bump behavior now preserves version format
- No longer automatically adds build numbers
- Use
--add-build-number
to explicitly add build numbers - Use
--no-build-number
to remove build numbers - Existing versions with build numbers will maintain their format
- Improved compatibility with pub.dev versioning requirements
-
Refactored git operations into separate commit command
-
Maintained backward compatibility with --auto-commit flag
-
Improved code reuse between bump and commit commands
1.1.0 - 2024-02-08 #
Added #
- New
--auto-commit
flag to control automatic git operations during version bumps - By default, version bumps no longer automatically create git commits or tags
- Users can opt-in to automatic git operations by using the
--auto-commit
flag - When enabled, the tool will:
- Update the version in pubspec.yaml
- Stage changes with
git add
- Create a commit with the message:
build(version): Bump version to {new_version}
- Create a git tag with the new version
1.0.0 - 2024-02-07 #
Added #
- Updating versions without build numbers (1.0.0 -> 2.0.0)
- Keeping versions without build numbers when bumping (1.0.0 -> 1.1.0)
- Converting between formats as needed
- Maintaining existing build numbers with --no-build-number-update
- Command implementation validates flag combinations
- Documentation updated in both README.md and version_management.md with clear examples
- Added semver version bumping functionality to the CLI tool. Users can now bump major (x.0.0), minor (0.x.0), or patch (0.0.x) versions using --major, --minor, or --patch flags respectively. The functionality is fully tested and can be combined with existing date-based build numbers. Example usage: