Skip to content

chore: merge main into next after v0.6.1 - #343

Merged
T-Crypt merged 4 commits into
nextfrom
T-Crypt/main-into-next-v0.6.1
Nov 15, 2026
Merged

T-Crypt merged 4 commits into
nextfrom
T-Crypt/main-into-next-v0.6.1

Conversation

@T-Crypt

@T-Crypt T-Crypt commented Nov 15, 2026

Copy link
Copy Markdown
Owner

Brings the v0.6.1 release (#342) into next: the CHANGELOG section, new harbor screenshots, the SCHEDULE tab in the README and harbor guide, the narrow phone tab bar fix, and the TestScheduleRoutes clock fix. After the merge, next has the same tree as main.

proof.sh passes.

Moves the Unreleased fixes under v0.6.1: the gateway holds a request while
its engine's lease drains, a minimum turn needs a served request, and an
engine with no in-flight figure reads as unknown.

The harbor screenshots are new and the README and harbor guide show the
SCHEDULE tab. Under 340 pixels the bottom tab bar drops its letter spacing
and side padding, so SCHEDULE no longer runs into ENGINES.
Between 23:00 and 23:30 on the node's clock, "23:00" read as tomorrow and
"23:30" as today, so the expected clash never came and TestScheduleRoutes
failed for half an hour a day. Both bookings now name tomorrow's date.
@T-Crypt
T-Crypt merged commit 92a0f62 into next Nov 15, 2026
4 checks passed
@T-Crypt
T-Crypt deleted the T-Crypt/main-into-next-v0.6.1 branch November 15, 2026 23:13
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.

1 participant