Repository navigation
chore(quest): move MoQ's wait to m1 and instant-acme to m3 - #295
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
This run was cancelled before it finished. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
MoQ is moving its switch to rind into its m1 (moq-dev/moq#7749) and dropping moq-relay's ACME for now, so it no longer waits on instant-acme 0.9. rind's quests still had
moq-on-rindin m3 and the instant-acme release in m1.Approach
Decided by the maintainer on 2026-11-03:
quest/m3/moq-on-rind.mdtoquest/m1/moq/moq-on-rind.mdand lists it in the MoQ epic.instant-acme-release.mdandinstant-acme-publish.mdfromquest/m1/moq/toquest/m3/, with a note in the MoQ epic saying why.quest/m1/rind/path.Impact
(Written by Claude Opus 5.5)
🤖 Generated with Claude Code