Repository navigation
chore(release): v0.6.1 - #342
Merged
Merged
Conversation
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Releases v0.6.1 from
main.nexthas the same tree asmain(#341 brought #338 and #340 over), so there is nonextmerge in this PR.In this release
docs/harbor.mdnow show the SCHEDULE tab (newassets/preview-schedule.png, a SCHEDULE section in the harbor guide, "five tabs").CHANGELOG
[Unreleased]becomes[v0.6.1] - 2026-11-15, the README status line says v0.6.1, and the roadmap has a v0.6.1 entry.Also
TestScheduleRoutesbooked "23:00" and then "23:30" and expected a clash. Between 23:00 and 23:30 on the clock, "23:00" means tomorrow and "23:30" means today, so the test failed for half an hour a day. It failed on this PR at 23:02 UTC, andTZ=UTC go test -run TestScheduleRoutes ./internal/gateway/reproduced it at 23:03. Both bookings now give tomorrow's date, and the same command passes at 23:04 (also under America/Denver and Pacific/Kiritimati).Proof
proof.shpasses: build, gofmt, vet,go test ./..., the Windows build and vet, golangci-lint 2.14.0.