![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
git-flow-versionbumping
Advanced tools
Automatically update the version property in package.json or composer.json when starting a release or hotfix through git flow.
Version bumping for git-flow (AVH Edition).
This package updates your version in either the composer.json file or package.json file based on the version from either the git flow release start
command or the git flow hotfix start
command. If a composer.json file is present in your git project, the version property will be updated. If the composer.json file is not present, the package will look for a package.json file and update the version there.
Version bumping should not be used if the php project is published to packagist as this might cause conflicts when a version
property exists in composer.json.
Install globally through npm
npm install --global git-flow-versionbumping
Update your global git config with the correct path to the package.
git config --global gitflow.path.hooks /path/to/git-flow-hooks
If you are unsure of where your global npm packages are located, run the following command: npm root
Enable the package either per-project or globally.
In order to enable version bumping for your project, run the following command inside your project: git config gitflow.versionbumping true
. In order to enable it globally, run the following command: git config --global gitflow.versionbumping true
.
If you want tag messages to be automated (you won't be bothered with your editor to specify it), use the following configuration options:
git config gitflow.hotfix.finish.message "Hotfix %tag%"
git config gitflow.release.finish.message "Release %tag%"
MIT License.
FAQs
Automatically update the version property in package.json or composer.json when starting a release or hotfix through git flow.
The npm package git-flow-versionbumping receives a total of 7 weekly downloads. As such, git-flow-versionbumping popularity was classified as not popular.
We found that git-flow-versionbumping demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 open source maintainers 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
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.