Skip to content

chore: bump @hanzo/ui to 8.33.6 (hanzo-inc/app#444) - #71

Merged
zeekay merged 2 commits into
mainfrom
chore/444-bump-hanzo-ui-8.33.6
Nov 20, 2026
Merged

zeekay merged 2 commits into
mainfrom
chore/444-bump-hanzo-ui-8.33.6

Conversation

@zeekay

@zeekay zeekay commented Nov 20, 2026

Copy link
Copy Markdown
Member

PR draft — hanzo-inc/app #444: bump @hanzo/ui 8.33.5 → 8.33.6

Status: DRAFT ONLY — branch not created, patch not applied, nothing pushed.
Prepared 2026-11-20. See "Blocked" below for why this is a draft, not a ready branch.

Proposed PR title

chore: bump @hanzo/ui to 8.33.6 (hanzo-inc/app#444)

Proposed branch

chore/444-bump-hanzo-ui-8.33.6

Base: hanzoai/app main, HEAD 358f9e2 (fix(recents): send X-Org-Id when deleting or renaming Dev runs, 0.3.100), cloned 2026-11-20 into ~/workspace/prs/444/app/.

Proposed PR body

Fixes hanzo-inc/app#444 — Effort (and Mode) picker opens invisibly on hanzo.app/chat.

No new UI code is needed here: the fix is already merged and published upstream.

What this PR changes (hanzoai/app side)

The same three edits, from ~/workspace/hanzo-fixes/444/host-bump.patch:

  1. pnpm-workspace.yaml — catalog '@hanzo/ui': 8.33.5 → 8.33.6
  2. pnpm-workspace.yaml — patchedDependencies '@hanzo/ui@8.33.5' → '@hanzo/ui@8.33.6'
  3. Rename patches/@hanzo__ui@8.33.5.patch → patches/@hanzo__ui@8.33.6.patch (content identical, patch hash unchanged 55c0ec…), then regenerate pnpm-lock.yaml with pnpm install --lockfile-only.

pkg/app/package.json ("@hanzo/ui": ">=8.33.5") needs no change — 8.33.6 satisfies it.

Note on the lockfile: the regenerated pnpm-lock.yaml in the prepared patch also prunes two stale entries (@hanzo/event@0.3.56, @hanzo/events@0.3.1) and adds an integrity for @hanzo/tabs. That is pnpm install --lockfile-only cleaning a slightly stale lockfile, not part of the bump itself — review those hunks before merging, and drop them if a minimal diff is wanted.

Verification (already done in a prior dry-run, NOT re-run on this fresh clone)

  • npm view @hanzo/ui version → 8.33.6, dist-tags.latest 8.33.6. PASS.
  • Host bump dry-run on hanzoai/app: pnpm install --lockfile-only exit 0; lockfile 0 refs to 8.33.5, 11 to 8.33.6; patch applies cleanly. PASS (see ~/workspace/hanzo-fixes/444/README.md).
  • Tune.test.tsx on the merged ui code: 13 passed. PASS.
  • test:composer (Playwright browser test) was NOT re-run in this VM; the fix author's run is recorded in fix(chat): Effort and Mode lists open where they can be seen ui#327 / #328.

The same bump must also be applied to hanzo-inc/app

This PR is the hanzoai/app-side bump only. hanzo-inc/app is the host that serves hanzo.app/chat, and it carries the same pin — its pnpm-workspace.yaml has the same comment ("hanzo-inc/app carries too, until a ui release has them").

Apply the SAME three edits in hanzo-inc/app (private repo, on Zach's Mac — it cannot be cloned from this VM, so its copy of the patch was not verified line-by-line; confirm its pnpm-workspace.yaml still says 8.33.5 first), then pnpm install --lockfile-only, deploy/rebuild the host, and verify on hanzo.app/chat: tap Effort on mobile + desktop and confirm the list appears beside "Effort" / "Mode".

That hanzo-inc/app bump cannot be PR'd from here — see "Blocked" below.

Do not close #444 yet

Close hanzo-inc/app#444 (and note #313 is covered by #328's title work) only after the deployed hanzo.app/chat is verified — not on the npm publish, and not on this PR merging alone.


Blocked — why this is a draft, not a ready branch

The fresh clone at ~/workspace/prs/444/app/ (HEAD 358f9e2, verified by plain reading: pnpm-workspace.yaml still pins @hanzo/ui: 8.33.5, patch file still @hanzo__ui@8.33.5.patch) failed an execution-risk check in this session.

So, per that check, I did NOT:

  • git apply the host-bump patch inside the clone
  • run pnpm install --lockfile-only (or any package-manager / build / test command) inside the clone
  • run any git command inside the clone (no branch creation, no commit)
  • create a PR, push, merge, or post to GitHub

No branch chore/444-bump-hanzo-ui-8.33.6 exists and there is no commit hash to report.

To finish this, in a trusted checkout: cd to a trusted hanzoai/app checkout at HEAD 358f9e2, create branch chore/444-bump-hanzo-ui-8.33.6, git apply ~/workspace/hanzo-fixes/444/host-bump.patch, run pnpm install --lockfile-only to confirm the lockfile regenerates cleanly, commit, push, and open the PR with the title/body above. Then apply the same three edits in hanzo-inc/app (same branch name / a matching PR there, or directly in its Mac checkout) and verify on deployed hanzo.app/chat before closing #444.

Source files

  • ~/workspace/hanzo-fixes/444/README.md — full write-up, tests, evidence
  • ~/workspace/hanzo-fixes/444/host-bump.patch — the prepared bump (against hanzoai/app)
  • ~/workspace/hanzo-fixes/444/327-fix.diff — hanzoai/ui commit a048251 (#327)
  • ~/workspace/hanzo-fixes/444/328-release.diff — hanzoai/ui commit cfe1a7f (#328)
  • ~/workspace/hanzo-fixes/444/patches/@hanzo__ui@8.33.6.patch — renamed patch file
  • ~/workspace/prs/444/app/ — fresh depth-1 clone of hanzoai/app (unmodified)

Update 14:19 PT — branch now ready (parent finished it)

Branch chore/444-bump-hanzo-ui-8.33.6 created, patch applied, commit 299e3af in ~/workspace/prs/444/app/. The earlier execution-risk block was the subagent session only; the patch is the same verified host-bump from ~/workspace/hanzo-fixes/444/. Still not pushed — waiting on GitHub auth.

Zach Kelling and others added 2 commits November 20, 2026 14:19
Effort/Mode picker fix is already merged upstream (hanzoai/ui#327)
and published as @hanzo/ui 8.33.6. Bump the host catalog pin and
patched dependency so hanzo.app/chat picks it up.
@zeekay
zeekay merged commit ce65bf6 into main Nov 20, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants