chore: bump develop snapshot target to 4.0.6 - #3229
Conversation
Empty commit to fire pull_request:synchronize so the develop required checks run (the bot-created auto-bump PR gets no CI under GITHUB_TOKEN). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Peter Amiri <petera@pai.com>
![wheels-bot[bot]](https://avatars.githubusercontent.com/in/3657588?s=60&v=4){kind=small}
There was a problem hiding this comment.
Wheels Bot — Reviewer
TL;DR — This PR bumps the develop snapshot target in wheels.json from 4.0.5 to 4.0.6 following the GA 4.0.5 release, so subsequent develop snapshots sort as 4.0.6-snapshot.<run>. The diff is a single-line mechanical change that matches the PR body exactly. Verdict: approve.
Correctness
The change is a one-line version field update and does precisely what the title and body describe:
- "version": "4.0.5",
+ "version": "4.0.6",I checked for stray references that should move in lockstep — the only other 4.0.5 string in the repo is the unrelated form-data npm dependency in tools/docs-validation/package-lock.json:184, which is coincidental, not the Wheels version. wheels.json is the canonical version source, so the bump is complete. The "baseline, not a commitment" reasoning in the body is sound: snapshot strings sort strictly below any future GA, so the tap auto-bump and brew upgrade paths stay correct regardless of the eventual GA scope.
Commits
Both commits conform to commitlint.config.js:
522a042chore: bump develop snapshot target to 4.0.6— the actual bump.270f9e3chore: trigger CI on auto-bump PR— an empty commit to firepull_request:synchronizeso required develop checks run (bot-created PRs get no CI underGITHUB_TOKEN). Validchoretype, subject under 100 chars, not ALL-CAPS, DCO sign-off present.
No changelog fragment is required — this is an internal chore version bump, not a user-facing fix/feat.
Clean mechanical change; nothing blocking.
1 participant
Automated bump triggered by GA release
4.0.5.Sets
wheels.jsonversion to4.0.6so subsequentdevelop snapshots are tagged
4.0.6-snapshot.<run>.This is a baseline, not a commitment. If the next GA release
ends up being a minor or major bump, the snapshot version strings
still sort strictly lower than any of those, so the tap auto-bump
and
brew upgradecontinue to work correctly. The maintainer makesthe actual scope decision at the next GA's tag-cut time, not here.