Repository navigation
Conversation
The fix landed on release in #6217. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 37 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Keep the quest deletion over main's verification rewrite, and drop the release-backports references to it so quest check passes once it merges. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a2f876f50f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| [moq-dev/moq#6217](https://github.com/moq-dev/moq/pull/6217). Verify its release | ||
| deploy reaches moq.dev, then retire this quest; no duplicate backport is |
There was a problem hiding this comment.
Keep the quest until the moq.dev rollout is verified
When #6217 is only merged to release and the deploy is still pending, as the commit message states, deleting this quest marks its Goal complete even though it explicitly requires verifying the deployed revision and numeric-delay behavior. This removes the only tracked follow-up for validating the known production regression; retain the quest until the release reaches moq.dev and the live check passes.
AGENTS.md reference: AGENTS.md:L47-L47
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Agreed, and this PR is gated on exactly that. It stays a draft until moq.dev serves a bundle with the fix. As of now it does not (evidence), so the remaining steps are listed under ## Decisions needed in the description.
(Written by Claude Opus 5.5)
|
Deploy check (2026-10-22): moq.dev does not serve the fix from moq-dev/moq#6217 yet, and no automatic deploy will bring it.
To unblock:
Then this PR can be marked ready. (Written by Claude Opus 5.5) |
Fixed-delay rollout status (2026-10-23 16:05 UTC)
(Written by Claude Opus 5.5) |
Main already retired the release-backports epic and the resubscribe-hang quest; keep this PR's deletion of the fixed-delay quest. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Closing as superseded by #6592, which has merged. (Written by Claude Opus 5.5) |
Deletes
quest/m0/release-fixed-delay.mdand its m0 README entry. The fix landed onreleasein moq-dev/moq#6217. moq.dev only picks it up from npm.No code, public API, or wire impact.
quest checkpasses.Decisions needed
This waits on the maintainer deploying moq.dev (
just deploy live). moq-dev/moq.dev#195 merged@moq/watch^0.6.6, which contains the fix, but moq.dev only deploys by hand. After the deploy, check that the bundle moq.dev serves uses a numeric delay as-is, then mark this ready (current evidence).(Written by Claude Opus 5.5)
🤖 Generated with Claude Code