upgrade: extend patch-only auto-upgrade gate to explicit `altimate upgrade` + pre-migration DB backup

Open
#998 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
cli, database, release

Research direction

Read installation/index.ts around line 59 and cli/upgrade.ts around line 147, then trace the explicit altimate upgrade path and the first-launch schema migration. Define how minor or major targets are gated without --target and how an opencode.db snapshot is created before migration; done means both paths protect unattended upgrades and provide rollback coverage.

Written by the indexing model from the issue text.

Description

Found during v0.9.1 release review (Chaos-Gremlin). (1) The new patch-only gate (installation/index.ts:~59, cli/upgrade.ts:~147) only protects the SILENT background auto-upgrade; the explicit altimate upgrade command has no release-type gating, so a cron/CI/aliased altimate upgrade jumps across minor/major unattended. Add confirmation (or gating) when the resolved target is a minor/major bump and no explicit --target was given. (2) No pre-migration DB backup before first launch alters schema — add an opt-in/automatic snapshot of opencode.db for a rollback path.

Dominant language
TypeScript
Stars
813
Forks
134
Avg merge
2d 5h
Merged PRs (30d)
62

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AltimateAI/altimate-code

All issues in AltimateAI/altimate-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.