Skip to content

chore: bump quest to v0.20.0 - #862

Merged
moq-bot[bot] merged 1 commit into
mainfrom
quest-bump
Nov 17, 2026
Merged

moq-bot[bot] merged 1 commit into
mainfrom
quest-bump

Conversation

@moq-bot

@moq-bot moq-bot Bot commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

Bumps the quest input, github:moq-dev/quest, from 7ab77ba to release v0.20.0 (a27c974): https://github.com/moq-dev/quest/releases/tag/v0.20.0

Changes: moq-dev/quest@7ab77ba...a27c974

quest init and quest check --fix with 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.

@moq-bot
moq-bot Bot enabled auto-merge November 17, 2026 11:04
@coderabbitai

coderabbitai Bot commented Nov 17, 2026

Copy link
Copy Markdown

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters: 1

  • flake.lock is excluded by !**/*.lock

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 78c1f246-f912-43c5-9a0e-47c59320fc12

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

@kixelated kixelated left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No new issues found.

Reviewed changes

Reviewed the full diff, a single flake.lock change.

  • quest pin bump — lastModified, narHash and rev move to a27c974 (v0.20.0), which matches the PR description. Nothing else in the lock changes.

Pullfrog  | View workflow run | Using claude-sonnet-5-5 | 𝕏

@moq-bot
moq-bot Bot added this pull request to the merge queue Nov 17, 2026
Merged via the queue into main with commit 4282cba Nov 17, 2026
7 checks passed
@moq-bot
moq-bot Bot deleted the quest-bump branch November 17, 2026 11:20
@codspeed

codspeed Bot commented Nov 17, 2026

Copy link
Copy Markdown

Merging this PR will improve performance by 13.33%

2 warnings

⚠️ 36 benchmarks are dominated by system calls

System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.

Learn more about system calls

See affected benchmarks

⚠️ 1 benchmark with a significant change ran on different hardware

Its base and head results were measured on machines with a different CPU, core count or memory, so the change might not come from the code. Run base and head on the same runner type.

Learn more about Macro Runners

See affected benchmarks

⚡ 1 improved benchmark
✅ 82 untouched benchmarks

Performance Changes

Benchmark BASE HEAD Efficiency
⚡ ready 7.3 s 6.5 s +13.33%

Tip

Curious why performance improved? Comment @codspeedbot explain why performance improved on this PR, or directly use the CodSpeed MCP with your agent.


Comparing quest-bump (153fed8) with main (3c05cb9)

Open in CodSpeed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant