Repository navigation
Promote dev base version after official 0.11 release #1455
Description
Problem
The official release is now 0.11, but the dev branch still uses 0.10 as the base version. This leaves prerelease/dev versioning anchored to the previous official release.
Goal
Update dev so its base version reflects 0.11, and add automation so future official releases from main promote the dev base version automatically.
Acceptance Criteria
- Dev branch version metadata is updated from 0.10 to 0.11 wherever the base version is defined.
- Release automation ensures that when an official release is made from main, dev is promoted to the new official base version without manual follow-up.
- The automation is documented or discoverable in the release workflow.
npm run buildpasses.
Notes
Reported after official version 0.11 was released.
Metadata
Metadata
Assignees
Labels
No labels
Activity
chore: add auto version-promote workflow for dev branch
chore: add auto version-promote workflow for dev branch (#1457)
chore: promote dev -> main (v0.12.0) (#1698)
bradygaster commentedon Aug 23, 2026
Closing — the problem statement is moot.
This asked to move the dev base version off
0.10after the official0.11release. Dev has since been promoted twice:chore(release): prepare v0.12.0chore: bump dev to 0.13.0 for next cycledevis at 0.13.0 today, so the original drift is gone.One acceptance criterion did not ship: "Release automation ensures that when an official release is made from main, dev is promoted to the new official base version without manual follow-up." Both promotions above were manual chore commits. Closing this rather than leaving a stale 0.10-era issue open — if the automation is still wanted, a fresh issue scoped purely to that (post-release dev promotion in the release workflow) would be clearer to pick up than this one.
Triage: 2026-08-23.