bump-version
/bump-version
Bump the Flutter app version in pubspec.yaml (major, minor, patch or build number) and open a matching CHANGELOG section. Use when the user says "bump version", "new release version", "increase build number", "prepare 2.0", or when release-check reports the current version was already tagged.
- Author
- ChandraChaan ↗
- Repository
- flutter-release-kit ↗
- Licence
- MIT
- Last repository change
- 08.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 08.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Bump the Flutter app version in pubspec.yaml (major, minor, patch or build number) and open a matching CHANGELOG section. Use when the user says "bump version", "new release version", "increase build number", "prepare 2.0", or when release-check reports the current version was already tagged.
Triggers from the description
Arguments
/bump-version major|minor|patch|build|exact X.Y.Z+N [--dry-run]
Original author description
Bump the Flutter app version in pubspec.yaml (major, minor, patch or build number) and open a matching CHANGELOG section. Use when the user says "bump version", "new release version", "increase build number", "prepare 2.0", or when release-check reports the current version was already tagged.
How it works
- Decide the bump
- Run
- After the bump
SKILL.md preview
---
name: bump-version
description: Bump the Flutter app version in pubspec.yaml (major, minor, patch or build number) and open a matching CHANGELOG section. Use when the user says "bump version", "new release version", "increase build number", "prepare 2.0", or when release-check reports the current version was already tagged.
argument-hint: "major|minor|patch|build|exact X.Y.Z+N [--dry-run]"
allowed-tools: Bash(python3 ${CLAUDE_PLUGIN_ROOT}/scripts/bump_version.py *), Bash(git log *), Bash(git describe *), Read
---
# Bump version
Flutter keeps one version string in `pubspec.yaml`: `version: 1.4.2+37`. The part before `+` is the user-visible version name (`versionName` / `CFBundleShortVersionString`); the number after `+` is the build number (`versionCode` / `CFBundleVersion`). Stores reject an upload whose build number is not higher than the last one, so the build number must always go up, even for a hotfix.
## Decide the bump
If the user did not say which part, look at what changed since the last tag (`git log $(git describe --tags --abbrev=0)..HEAD --oneline`):
- breaking change, redesign, large new feature group → `major`
- new user-facing features → `minor`
- fixes only → `patch`
- rebuilding the same code for a store re-upload → `build`
Tell the user your choice in one line before running it.
## Run
```bash
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/bump_version.py" $ARGUMENTS
```
Use `--dry-run` first when the user seems unsure. The script:
1. rewrites the `version:` line in `pubspec.yaml`, always incrementing the build number;
2. turns an `## [Unreleased]` section in `CHANGELOG.md` into the new version, or inserts an empty dated section at the top;
3. prints the commit and tag commands.
Pass `--no-changelog` for projects without a changelog that do not want one.
## After the bump
- If the new changelog section has empty bullets, run the `changelog` skill (or draft bullets yourself from the git log) so it is not committed empty.
- Suggest, but do not run unprompted:
```bash
git commit -am "chore: release X.Y.Z+N"
git tag vX.Y.Z
```
- Remind the user that iOS also reads `CFBundleShortVersionString` and `CFBundleVersion` from `$(FLUTTER_BUILD_NAME)` / `$(FLUTTER_BUILD_NUMBER)` in `Info.plist`. If those were hard-coded, the pubspec bump will not reach iOS; fix the plist to use the variables.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · ChandraChaan/flutter-release-kit | 100 | MIT |
| membrowse/membrowse-action | 100 | GPL-3.0 |
| lorem-dev/duolog | 100 | Apache-2.0 |
| waldekmastykarz/vally-claudecodecli | 100 | MIT |
| cassandragargoyle/skill-source-trust-assessment | 100 | MIT |
| iofficeai/aionui | 100 | Apache-2.0 |
| sd0xdev/sd0x-harness | 100 | MIT |
| hyhmrright/logic-lens | 100 | MIT |
| quantumbfs/sci-brain | 100 | MIT |
Database snapshot: 13.11.2026 · package version 7696f2983809 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100changelog
Generate a changelog section or store "What's new" release notes from git history for a Flutter app. Use when the user asks for release notes, "what's new text", "changelog for this version", or when bump-version left an empty section. - 100release
Cut a new release: group Conventional Commits since the last tag, append a CHANGELOG section, create a release commit, and add an annotated git tag. TRIGGER when the user says "cut a release", "tag a release", "release v1.2.0", "ship version 1.2.0", "create a release for 1.2.0",… - 100version
This skill should be used when the user wants to bump versions, create releases, or tag versions. Triggers include: "bump version", "bump the version", "version bump", "release version", "tag a release", "create release", "major/minor/patch bump", "update version", "new… - 90bump
This skill should be used when the user asks to "bump version", "bump new version", "release new version", "update version", "create a release", or any task involving incrementing the crux-hive plugin version, updating the changelog, and creating a release PR. - 100version-bump
Increment app version numbers. Use when user asks to bump version, increment version, or prepare a release. - 100new-release
Prepare a Graphmem release or version bump. Use whenever the user asks to release, cut a version, bump a patch/minor/major version, update the changelog, or synchronize Graphmem, OpenCode/pi, Claude Code, and Codex plugin versions.