A Gulp plugin to bump Semantic Versioning (semver) numbers in any file type.
gulp-bump is a Gulp plugin that automatically increments version numbers in project files using Semantic Versioning (semver). It solves the problem of manually updating version strings across multiple configuration files during software releases, ensuring consistency and reducing human error. The plugin integrates seamlessly into Gulp-based build pipelines for automated version management.
Developers and teams using Gulp as their build system who need to automate version bumps in JSON, YAML, or other configuration files as part of their release process.
Developers choose gulp-bump for its simplicity, flexibility with file types and version keys, and tight integration with Gulp workflows. It eliminates manual version updates, enforces semver compliance, and works across multiple files simultaneously.
Bump any version in any file which supports semver with gulp (gulpjs.com)
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Enforces semantic versioning rules for major, minor, patch, and prerelease increments, as shown in the examples with options like {type:'minor'} in the README.
Updates version numbers across multiple configuration files (e.g., package.json, bower.json) in a single Gulp task, streamlining release workflows as demonstrated in the usage examples.
Allows specifying custom version keys like 'appversion' for non-standard JSON files, providing flexibility for diverse project setups, illustrated in the options section.
Works with any file type containing semver-compatible strings, including JSON and YAML, making it versatile for different project configurations, as seen in the package.yml example.
Version 2 no longer creates the version key if it does not exist in the file, which can cause errors if not handled manually, as noted in the README's breaking changes section.
Designed for Gulp 3.x, an older version, and may not be fully compatible with Gulp 4 or newer build systems without adjustments, limiting its use in modern setups.
Primarily useful only within Gulp workflows; projects using other build tools or CI/CD pipelines without Gulp will find it irrelevant, reducing its broader applicability.