Repository navigation
chore: bump quest to v0.17.1 - #855
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) · d24e005b39696b22569b8cc869f53f737960d460
This pin includes Quest #763, which can publish a failed fixer's mixed stdout/stderr in a PR comment. The released filter covers GitHub token formats, not other private content. If this pin supplies a live land watcher, keep that watcher on the prior version until handbacks use a public-safe launcher diagnostic. The development pin alone does not establish that the watcher has upgraded. Static review only; no watcher changes made.
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
Reviewed the single flake.lock change in this run.
questpin bump —rev,narHashandlastModifiedmove fromf293c54toae12957(v0.17.1). No repository code changes.
claude-sonnet-5-5 | 𝕏
Merging this PR will degrade performance by 3.7%1 warning
Warning Please fix the performance issues or acknowledge them on CodSpeed. Performance Changes
Tip Investigate this regression by commenting Comparing Footnotes |

Bumps the
questinput, github:moq-dev/quest, fromf293c54to release v0.17.1 (ae12957): https://github.com/moq-dev/quest/releases/tag/v0.17.1Changes: moq-dev/quest@f293c54...ae12957
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.