Skip to content

Rehearse the Homebrew upgrade contract for 1.0.0 #526

Description

@codeforester

Problem

Issue #516 documented the Homebrew tap release update process, but 1.0.0 also needs a proven consumer upgrade contract. Existing users will expect brew upgrade codeforester/base/base to preserve their ~/.base.d state, keep shell profile behavior sane, and leave basectl usable without manual repair.

Desired outcome

Before 1.0.0, run and document a repeatable Homebrew upgrade rehearsal from an existing released Base version to a 1.0.0 release candidate or equivalent test formula.

Scope

  • Start from a machine or test account with an existing Homebrew Base install.
  • Run basectl setup so local Base state and shell integration exist before the upgrade.
  • Upgrade through the Homebrew tap path.
  • Verify BASE_HOME, shell profile integration, Base venv state, and project discovery still work.
  • Verify at least one Base-managed project can run basectl check, basectl doctor, and basectl test after upgrade.
  • Record the exact rehearsal commands and observed results in the release checklist or a linked validation note.

Non-goals

  • Do not replace the Homebrew tap release process already documented in Document Homebrew tap release update process #516.
  • Do not require automated installation of Homebrew itself in this issue.
  • Do not broaden this into full Linux or clean-install validation; those are covered by separate work.

Acceptance criteria

  • brew upgrade codeforester/base/base succeeds from an existing released install to the candidate under test.
  • Existing ~/.base.d project state is preserved.
  • Shell startup still points at the upgraded Base installation.
  • A Base-managed project can run setup/check/doctor/test successfully after the upgrade.
  • Any breakage found during the rehearsal is either fixed or filed as a blocking follow-up before 1.0.0.

Validation

Use the release process in docs/release-process.md as the starting point, then add the concrete upgrade rehearsal evidence for the 1.0.0 candidate.

Demo impact

This closes the gap between a documented release ceremony and a trustworthy user-facing upgrade experience.

Metadata

Metadata

Assignees

Labels

ciContinuous integration, tests, automation, or release workflowsenhancementNew feature or product improvement

Type

No type

Projects

Status
Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions