BUMPVERSION(1)
β¨ NAME β¨
bumpversion β version-bump your software, bestie π (it's the manual page, and it's serving)
π¦ DESCRIPTION π¦
okay so real talk, this is literally the usage of bumpversion, here's the whole thing:
bumpversion [-h] [--config-file FILE] [--verbose] [--list]
[--allow-dirty] [--parse REGEX] [--serialize FORMAT] [--search
SEARCH] [--replace REPLACE] [--current-version VERSION]
[--no-configured-files] [--dry-run] --new-version VERSION
[--commit | --no-commit] [--tag | --no-tag] [--sign-tags |
--no-sign-tags] [--tag-name TAG_NAME] [--tag-message TAG_MESSAGE]
[--message COMMIT_MSG] [--commit-args COMMIT_ARGS] part [file
...]
and the version check moment:
bumpversion: v1.0.1 (using Python v3.9.7)
π POSITIONAL ARGUMENTS π
partβ which lil slice of the version is getting bumped. that's the whole assignment. πfileβ the files you wanna change (default:[]) π
π OPTIONAL ARGUMENTS π
-h,--helpβ shows this help message and dips. classic. (default behavior: shows help and exits) β¨--config-file FILEβ the config file it reads most of the variables from (default:.bumpversion.cfg) π--verboseβ prints verbose logging tostderr(default:0) β turn it up, get the tea π«--listβ list machine readable information (default:False) π€--allow-dirtyβ don't abort if the working directory is dirty (default:False) β chaotic energy, respect π«Ά--parse REGEXβ the regex that parses the version string (default:(?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)(\-(?P<release>[a-z ]+))?)) π--serialize FORMATβ how to format what's parsed back into a version (default:['{major}.{minor}.{patch}-{release}', '{major}.{minor}.{patch}']) π§--search SEARCHβ template for the complete string to search (default:{current_version}) π--replace REPLACEβ template for the complete string to replace (default:{new_version}) π--current-version VERSIONβ the version that needs to be updated (default:1.0.1) π--no-configured-filesβ only replace the version in files specified on the command line, ignoring the files from the configuration file (default:False) π--dry-run,-nβ don't write any files, just pretend. (default:False) β manifesting only, no cap β¨--new-version VERSIONβ the new version that should be in the files (default:None) π--commitβ commit to version control (default:True) πΎ--no-commitβ do not commit to version control π«--tagβ create a tag in version control (default:True) π·οΈ--no-tagβ do not create a tag in version control π«--sign-tagsβ sign tags if created (default:False) βοΈ--no-sign-tagsβ do not sign tags if created π«--tag-name TAG_NAMEβ tag name (only works with--tag) (default:v{new_version}) π·οΈβ¨--tag-message TAG_MESSAGEβ tag message (default:Bump version: {current_version} ??? {new_version}) π¬--message COMMIT_MSG,-m COMMIT_MSGβ commit message (default:Bump version: {current_version} ??? {new_version}) π¬--commit-args COMMIT_ARGSβ extra arguments to commit command (default: ``) β
ngl bestie, if you're doing a --dry-run first, you're the main character. periodt. π
π SEE ALSO π
The full documentation for bumpversion is maintained as a Texinfo manual. If the info and bumpversion programs are properly installed at your site, the command
info bumpversion
should give you access to the complete manual. π
that's the whole vibe check, babe π bumpversion 1.0.1, November 2021, BUMPVERSION(1) β ok bye love u, go bump responsibly ππ¦πΈ
π¦ where this page comes from
- debian bookworm: bumpversion 1.0.1-1 Β· MIT
- ubuntu jammy: bumpversion 1.0.1-1 Β· MIT
- ubuntu noble: bumpversion 1.0.1-1 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms