cog-bump(1)
π COG-BUMP(1) π
okay so bestie, welcome to cog-bump β it's a General Commands Manual situation, and I'm gonna walk you through it like we're on FaceTime at 1am π
β¨ NAME β¨
cog-bump β commit changelog from latest tag to HEAD and create new tag
like, literally that's the whole vibe: it writes your changelog from the latest tag up to HEAD, then slaps a new tag on it. icon behavior fr π«Ά
πΈ SYNOPSIS πΈ
cog-bump [--version] [-a|--auto] [-M|--major] [-m|--minor] [-p|--patch]
[--pre] [--build] [-H|--hook-profile] [--package] [-A|--annotated]
[-d|--dry-run] [--skip-ci] [--skip-ci-override] [--skip-untracked]
[--disable-bump-commit] [--include-packages] [-h|--help]
copy it exactly bestie, don't be creative with the flags π
π¦ DESCRIPTION π¦
Commit changelog from latest tag to HEAD and create new tag.
that's it. that's the whole personality. it takes everything between your latest tag and HEAD, turns it into a changelog commit, and then makes you a shiny new tag. no cap, it's giving "release day but make it automated" β¨
π OPTIONS π
--version <VERSION>β you set the target version yourself, manually, with your own two hands. main character energy π-a,--autoβ let it auto-suggest the target version for you. it's got you, babe π«Ά-M,--majorβ increment the major version. big moves only π₯-m,--minorβ increment the minor version. cute, modest, effective πΈ-p,--patchβ increment the patch version. tiny little fix, still iconic π--pre [<PRE>]β set the pre-release version (e.g."beta.1")
or increment it based on a pattern (e.g. "beta.*") β yes bestie, the wildcard is real β
if you don't give it a value at all, it falls back to the pre defined in cog.toml. no drama, it just checks the config π
--build <BUILD>β set the build suffix. garnish for your version string π-H,--hook-profile <HOOK_PROFILE>β specify the bump profile hooks to run. like picking which playlist plays during your release π--package <PACKAGE>β specify which package to bump for monorepo. one package gets the spotlight π-A,--annotated <ANNOTATED>β annotate the tag with the message you give it π-d,--dry-runβ dry-run: print the target version. no action taken. literally nothing happens, it's just a vibe check π--skip-ciβ add the skip-ci string defined in thecog.toml(or defaults to[skip ci]) to the bump commit. tells CI to sit this one out π€--skip-ci-override <SKIP_CI_OVERRIDE>β override and add the skip-ci string with the value you provide to the bump commit. you're the boss of the string now π₯--skip-untrackedβ don't fail if there are untracked or uncommitted files. let it slide π--disable-bump-commitβ disable the creation of the bump commit. no commit, just tag energy β--include-packagesβ also bump packages on manual bump
this overrides the default behaviour for --patch, --minor, --major and --version to only bump the global version for monorepos. useful to bump to version 1.0.0 π
-h,--helpβ print help (see a summary with'-h'). the classic π«Ά
ngl bestie, peep that-hnote:-hgives you the short summary,--helpgives you the whole essay. iykyk π
and that's the tea β β this page, cog-bump(1), is from the cog-bump manual (General Commands Manual), version cog-bump, dated cog-bump(1). mwah, go tag something beautiful ππβ¨
π¦ where this page comes from
- arch rolling: cocogitto 7.0.0-3 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms