Repository navigation
chore: bump quest to v0.20.0 - #9006
Conversation
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed 1fe117caad07f4526461e0ac386eda6d23d1c9de. Hold this pin on hosts that run the Quest records sender until the queue migration is addressed. v0.20.0 is the first release that includes Quest #767. The new sender ignores endpoint information already stored on queued sessions and re-resolves them against the current Kixel Quest server. It can settle queued records an unrelated catalog doesn't list, and an upload 403 for one repository settles the host's whole queue. A green flake or quest check doesn't exercise that upgrade. The changed path requires the records sender and configuration; I did not verify an active sender on a host for this repository.
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
Reviewed the single flake.lock change in this PR.
questpin bump — updates the lockedquestinput (rev,narHash,lastModified) from7ab77batoa27c974(v0.20.0). Nothing else changes.
claude-sonnet-5-5 | 𝕏

Bumps the
questinput, github:moq-dev/quest, from7ab77bato release v0.20.0 (a27c974): https://github.com/moq-dev/quest/releases/tag/v0.20.0Changes: moq-dev/quest@7ab77ba...a27c974
quest initandquest check --fixwith the new quest changed nothing else.Review
Skipped: pin bump, no repository code changed; CI's quest check is the gate.
Opened by
quest land watch, which replaces this branch with each newer bump.