
Security News
Feross on TBPN: How North Korea Hijacked Axios
Socket CEO Feross Aboukhadijeh breaks down how North Korea hijacked Axios and what it means for the future of software supply chain security.
grunt-version-git
Advanced tools
Change version numbers in files, including the option to change the revision number to the number of Git commits.
Change version numbers in files, including the option to change the revision number to the number of Git commits.
This plugin requires Grunt ~0.4.1
If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:
npm install grunt-version-git --save-dev
Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
grunt.loadNpmTasks('grunt-version-git');
This task changes version numbers in files, including the option to change the revision number to the number of Git commits.
The task can make use of the git command and expects it to be globally installed.
In your project's Gruntfile, add a section named version_git to the data object passed into grunt.initConfig().
grunt.initConfig({
version_git: {
options: {
// Task-specific options go here.
},
your_target: {
// Target-specific file lists and/or options go here.
},
},
})
Type: Boolean|Number
Default value: false
Type: Boolean|Number
Default value: false
Type: Boolean|Number
Default value: true
Type: String
Type: Boolean
Default value: false
Appends a build number based on the number of GIT commits, ie: v1.2.3+897.
Type: Regexp|Regexp[]
Default value: /\d+\.\d+\.\d+/
Versioning options can be used by CLI, which is very useful for bumping majors and minors. The following overrides the setup from the gruntfile and sets the major version of all files:
grunt version_git --major=3
Other options are:
grunt version_git --minor=3
grunt version_git --patch=3
grunt version_git --vs="2.3.4"
In this example, the default options are used to do something with whatever. So if the testing file has the content Testing and the 123 file had the content 1 2 3, the generated result would be Testing, 1 2 3.
grunt.initConfig({
version_git: {
files: ['src/testing/file0.js']
}
})
/*
* Example
* @version 1.0.1
*/
(function(){
'use strict';
return {};
})();
In this example, custom options are used to do something else with whatever else. So if the testing file has the content Testing and the 123 file had the content 1 2 3, the generated result in this case would be Testing: 1 2 3 !!!
grunt.initConfig({
version_git: {
options: {
},
src: ['src/testing', 'src/123']
}
})
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.
(Nothing yet)
FAQs
Change version numbers in files, including the option to change the revision number to the number of Git commits.
We found that grunt-version-git demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Socket CEO Feross Aboukhadijeh breaks down how North Korea hijacked Axios and what it means for the future of software supply chain security.

Security News
OpenSSF has issued a high-severity advisory warning open source developers of an active Slack-based campaign using impersonation to deliver malware.

Research
/Security News
Malicious packages published to npm, PyPI, Go Modules, crates.io, and Packagist impersonate developer tooling to fetch staged malware, steal credentials and wallets, and enable remote access.