Repository navigation
chore: bump quest to v0.11.0 - #8685
Merged
Merged
Conversation
Maintainer settled each in /quest-complete 2026-11-13. route-trace-validation waits on #8622. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
kixelated
marked this pull request as ready for review
November 14, 2026 12:30
kixelated
force-pushed
the
quest-bump
branch
from
November 14, 2026 12:31
c968a55 to
4fd8669
Compare
Contributor
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes: the full diff, which only touches flake.lock.
questpin bump: moves thequestinput fromb30e26fto release v0.11.0 (33f4629), with a matchingnarHashandlastModified.- New transitive input: adds
token-max(kixel-ai/token-max, locked at83ab616). Itsflake-utils,nixpkgsandquestinputs followquest, so it adds no second copy of those.
claude-sonnet-5-5 | 𝕏
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.

Bumps the
questinput, github:moq-dev/quest, fromb30e26fto release v0.11.0 (33f4629): https://github.com/moq-dev/quest/releases/tag/v0.11.0Changes: moq-dev/quest@b30e26f...33f4629
quest initandquest check --fixwith the new quest changed nothing else. The cross-milestone findings the newquest checkreported are already resolved onmain(the milestone audit moq-dev/moq#8637 and moq-dev/moq#8622 moved those quests and dropped the deletedscope.mdlink), so after mergingorigin/mainthis branch changes onlyflake.lock, andquest check --base origin/main --branch HEADwith v0.11.0 is clean.Picks taken while the maintainer is away (/quest-afk): I did not apply the maintainer's 2026-11-13
quest mvpicks (buffered-ascending,export-order→ m3;receive-windows-evicted,routing-guide→ m2;formatter-defaults→ m5) or keeproute-trace-validationin m1, becausemainalready moved those quests (receive-windows-evicted,routing-guideandroute-trace-validationwent to m3, later than the picked m2/m1) and the newest decision wins. Decided 2026-11-14 (maintainer, /quest-complete): ✅ merge, keeping the audit's m3 placements (rejected: reapply the 2026-11-13 picks).Public API: none. Wire: none.
Models
Size: S
Implementer: Claude Code, claude-sonnet-5-5, unknown effort
Review
Skipped on head 6d617a2: pin bump, no repository code or quest changed; CI's quest check is the gate.
🤖 Generated with Claude Code