معرفی شرکت ها
bump-my-version-0.4.0
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشتر
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشتر
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشتر
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشتر
تبلیغات ما
مشتریان به طور فزاینده ای آنلاین هستند. تبلیغات می تواند به آنها کمک کند تا کسب و کار شما را پیدا کنند.
مشاهده بیشترتوضیحات
Version bump your Python project
| ویژگی | مقدار |
|---|---|
| سیستم عامل | - |
| نام فایل | bump-my-version-0.4.0 |
| نام | bump-my-version |
| نسخه کتابخانه | 0.4.0 |
| نگهدارنده | [] |
| ایمیل نگهدارنده | [] |
| نویسنده | - |
| ایمیل نویسنده | Corey Oordt <coreyoordt@gmail.com> |
| آدرس صفحه اصلی | - |
| آدرس اینترنتی | https://pypi.org/project/bump-my-version/ |
| مجوز | MIT License Copyright (c) 2013-2014 Filip Noetzel Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. |
# Bump My Version
[](https://pypi.org/project/bump-my-version/)
[](https://pypi.org/project/bump-my-version/)
[](https://pypi.org/project/bump-my-version/)
[](https://codecov.io/gh/callowayproject/bump-my-version)
[](https://github.com/callowayproject/bump-my-version/actions)
> **NOTE**
>
> This is a maintained refactor of the [bump2version fork](https://github.com/c4urself/bump2version) of the excellent [bumpversion project](https://github.com/peritus/bumpversion). The main goals of this refactor were:
>
> - Add support for `pyproject.toml` configuration files.
> - Convert to [click](https://click.palletsprojects.com/en/8.1.x/) for and [rich](https://rich.readthedocs.io/en/stable/index.html) for the CLI interface
> - Add better configuration validation using [Pydantic](https://docs.pydantic.dev)
> - Make the code and tests easier to read and maintain
## Overview
Version-bump your software with a single command!
A small command line tool to simplify releasing software by updating all version strings in your source code by the correct increment and optionally commit and tag the changes.
* version formats are highly configurable
* works without any source code manager, but happily reads tag information from and writes
commits and tags to Git and Mercurial if available
* just handles text files, so it's not specific to any programming language
* supports Python 3.8+ and PyPy3. Python 3.7 should work but isn't actively tested.
## Future Direction
- Make it easier to get the current version
- Switch having both the version part and files to change as arguments on the command line.
- Make the version part argument _truly_ optional when `--new-version` is specified
- Allow for multiple tags, including one that moves for having a `v2` that always points to the latest version of version 2.
- https://github.com/c4urself/bump2version/issues/253 Have an "always increment" configuration
- Better UI with [Rich](https://rich.readthedocs.io/en/stable/index.html)
- https://github.com/c4urself/bump2version/issues/267 Ignore-missing error in files flag
- https://github.com/c4urself/bump2version/issues/233 How are relative configured file paths resolved?
- https://github.com/c4urself/bump2version/issues/225 Properly resolve configuration file through parent directories when in a git or mercurial repo
**Documentation opportunities**
- https://github.com/c4urself/bump2version/issues/252
- https://github.com/c4urself/bump2version/issues/247
- https://github.com/c4urself/bump2version/issues/243
- https://github.com/c4urself/bump2version/issues/240
- https://github.com/c4urself/bump2version/issues/239
- Add dates to releases in changelog
- https://github.com/c4urself/bump2version/issues/200 Add CalVer examples
## Installation
You can download and install the latest version of this software from the Python package index (PyPI) as follows:
```console
pip install --upgrade bump-my-version
```
## Changelog
Please find the changelog here: [CHANGELOG.md](CHANGELOG.md)
## Usage
> **NOTE:**
>
> Throughout this document, you can use `bumpversion` or `bump-my-version` interchangeably.
There are two modes of operation: On the command line for single-file operation and using a configuration file for more complex multi-file operations.
bump-my-version [options] part [file]
### `part`
_**required**_
The part of the version to increase, e.g. `minor`.
Valid values include the named groups defined in the `parse` configuration.
Example bumping 0.5.1 to 0.6.0:
bump-my-version --current-version 0.5.1 minor
### `file`
_**[optional]**_<br />
**default**: none
Additional files to modify.
These files are added to the list of files specified in your configuration file. If you want to rewrite only files specified on the command line, also use `--no-configured-files`.
Example bumping 1.1.9 to 2.0.0:
bump-my-version --current-version 1.1.9 major setup.py
## Configuration file
`bump-my-version` looks in four places for the configuration file to parse (in order of precedence):
1. `--config-file <FILE>` _(command line argument)_
2. `BUMPVERSION_CONFIG_FILE=file` _(environment variable)_
3. `.bumpversion.cfg` _(legacy)_
4. `.bumpversion.toml`
5. `setup.cfg` _(legacy)_
6. `pyproject.toml`
`.toml` files are recommended due to their type handling. We will likely drop support for `ini`-style formats in the future due to issues with formatting and parsing. You should add your configuration file to your source code management system.
By using a configuration file, you no longer need to specify those options on the command line. The configuration file also allows greater flexibility in specifying how files are modified.
## Command-line Options
Most of the configuration values above can also be given as an option on the command line.
Additionally, the following options are available:
`--dry-run, -n`
Don't touch any files, just pretend. Best used with `--verbose`.
`--no-configured-files`
Will not update/check files specified in the configuration file.
Similar to dry-run, but will also avoid checking the files. Also useful when you want to update just one file with e.g., `bump-my-version --no-configured-files major my-file.txt`
`--verbose, -v`
Print useful information to stderr. If specified more than once, it will output more information.
`--list`
List machine-readable information to stdout for consumption by other programs.
Example output:
current_version=0.0.18
new_version=0.0.19
`-h, --help`
Print help and exit
## Using bumpversion in a script
If you need to use the version generated by bumpversion in a script, you can make use of the `--list` option combined with `grep` and `sed`.
Say, for example, that you are using git-flow to manage your project and want to automatically create a release. When you issue `git flow release start` you need to know the new version before applying the change.
The standard way to get it in a bash script is
bump-my-version --dry-run --list <part> | grep <field name> | sed -r s,"^.*=",,
where `part` is the part of the version number you are updating. You need to specify `--dry-run` to avoid bumpversion acting.
For example, if you are updating the minor number and looking for the new version number, this becomes
bump-my-version --dry-run --list minor | grep new_version | sed -r s,"^.*=",,
## Development & Contributing
Thank you, contributors! You can find a full list here: https://github.com/callowayproject/bump-my-version/graphs/contributors
See also our [CONTRIBUTING.md](CONTRIBUTING.md)
Development of this happens on GitHub, patches including tests, and documentation are very welcome, as well as bug reports! Please open an issue if this tool does not support every aspect of bumping versions in your development
workflow, as it is intended to be very versatile.
## License
bump-my-version is licensed under the MIT License - see the [LICENSE](LICENSE) file for details
نیازمندی
| مقدار | نام |
|---|---|
| - | click |
| - | pydantic |
| - | rich-click |
| - | rich |
| - | tomlkit |
| >=1.12.2 | git-fame |
| >=0.7.6 | generate-changelog |
| - | pip-tools |
| - | pre-commit |
| - | ghp-import |
| - | linkify-it-py |
| - | myst-parser |
| - | furo |
| >=4.3.0 | Sphinx |
| - | sphinx-autodoc-typehints |
| - | sphinx-click |
| - | sphinx-copybutton |
| - | coverage |
| - | pre-commit |
| - | pytest-cov |
| - | pytest |
| - | pytest-mock |
زبان مورد نیاز
| مقدار | نام |
|---|---|
| >=3.7 | Python |
نحوه نصب
نصب پکیج whl bump-my-version-0.4.0:
pip install bump-my-version-0.4.0.whl
نصب پکیج tar.gz bump-my-version-0.4.0:
pip install bump-my-version-0.4.0.tar.gz