Given this requirements.txt: Django>=1.5.6, | grep | sed -r s,”^.*=”,
Template to create the string that will replace the current version number in
Can be multiple lines, templated using Python Format String Syntax. Might be multiple times in the file and you mean to only bump one of the Useful if the remotest possibility exists that the current version number
SMBUP NEWEST VERSION HOW TO
Template string how to search for the string to be replaced in the file. Both acceptĭatetime formatting (when used like as in search = The variables now or utcnow to get a current timestamp. This is templated using the Python Format String Syntax.Īvailable in the template context are current_version and new_versionĪs well as all environment variables (prefixed with $). The name of the tag that will be created. If you are using git, don’t forget to git-push with theĪlso available on the command line as (-tag | -no-tag). Whether to create a tag, that is the new version, prefixed with the character
SMBUP NEWEST VERSION PATCH
to go from 0.5.1 directly toĠ.6.1: bumpversion -current-version 0.5.1 -new-version 0.6.1 patch setup.py). If not given will beĪlso available as -new-version (e.g. The version of the software package after the increment. bumpversion -current-version 0.5.1 patch setup.py) new_version = The current version of the software package before bumping.Īlso available as -current-version (e.g. General configuration is grouped in a section. bumpversion.cfg exists, bumpversion will also look into Which take precedence over those derived from the environment and then from the Options on the command line take precedence over those from the config file, You should add that file to VCS so others can also bumpversion.cfg so that once you know how bumpversion needs to beĬonfigured for one particular software package, you can run it without If no files are mentioned on theĬonfiguration file either, are no files will be modified.Įxample bumping 1.1.9 to 2.0.0: bumpversion -current-version 1.1.9 major setup.py ConfigurationĪll options can optionally be specified in a config file called If not given, the list of sections from theĬonfiguration file will be used.
Valid values include those given in the -serialize / -parse option.Įxample bumping 0.5.1 to 0.6.0: bumpversion -current-version 0.5.1 minor src/VERSION The part of the version to increase, e.g. There are two modes of operation: On the command line for single-file operationĪnd using a configuration file for more complex multi-file
SMBUP NEWEST VERSION INSTALL
You can download and install the latest version of this software from the Python package index (PyPI) as follows: pip install -upgrade bumpversion Usage Just handles text files, so it’s not specific to any programming language Works without any VCS, but happily reads tag information from and writesĬommits and tags to Git and Mercurial if available Version strings in your source code by the correct increment. Please contribute.Ī small command line tool to simplify releasing software by updating all 🔨If you want to help maintain bumpversion, there’s an ongoing discussion about merging the fork back to the original project as well as forming a group of maintainers to ensure a long-term future for this project. 🎬If you want to start using bumpversion, you’re best advised to install one of the maintained forks, e.g.
0 kommentar(er)
