max / makenotwork

Advance the quasi-type rev pin to the head of its pushed main The pinned rev f5e9e9c9 is two commits behind quasi-type's main, so the [patch] block built this against 55e74d77 locally while a container build took the older tree. Both revs are 0.1.3.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WFBzMprSmNCfvdj2cGZyka

Author: Max Johnson <me@maxj.phd> · 2026-09-08 12:14 UTC

Signed with PGP, not checked

Commit: 58b486c8ee87e0e069350f1c5c0c2c2b9fd39675

Parent: e01cc6f

1 file changed, +1 insertion, -1 deletion

M server/Cargo.toml +1 -1

			@@ -280,7 +280,7 @@
280	280		# and the terminal bundles. The three move together, in one pass, or a user sees
281	281		# two Quasi Monos. Under the tree's `[patch]` block the rev is ignored and the
282	282		# working copy is what builds.
283		-	quasi-type = { git = "https://makenot.work/git/max/quasi-type.git", version = "0.1.3", rev = "f5e9e9c96f32ec5e8c5b74089e6ec436c936e0b8" }
	283	+	quasi-type = { git = "https://makenot.work/git/max/quasi-type.git", version = "0.1.3", rev = "55e74d77" }
284	284		# Writes the two scripts the renderer ships into `static/`, from the constants
285	285		# the crate carries. They are the renderer's behaviour rather than the app's --
286	286		# a bulk bar's count, a readout that keeps ticking -- and the shell has always