Repository navigation
chore: bump quest to v0.20.0 - #862
Conversation
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters: 1
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including
|
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed 153fed83085719c3970072959d900524c9eb64c1. 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 full diff, a single flake.lock change.
questpin bump —lastModified,narHashandrevmove toa27c974(v0.20.0), which matches the PR description. Nothing else in the lock changes.
claude-sonnet-5-5 | 𝕏
Merging this PR will improve performance by 13.33%2 warnings
Performance Changes
Tip Curious why performance improved? Comment Comparing |

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.