Skip to content

feat(noq)!: build on moq-noq, the MoQ fork of noq - #398

Closed
kixelated wants to merge 1 commit into
mainfrom
moq-noq
Closed

kixelated wants to merge 1 commit into
mainfrom
moq-noq

Conversation

@kixelated

Copy link
Copy Markdown
Collaborator

Switches web-transport-noq from noq to moq-noq, the MoQ fork, per quest/next/quic/fork.md. The dependency is aliased back to noq, so the source and the web_transport_noq::noq re-export path are unchanged; only the crate behind them differs.

Public API impact: breaking. Every re-exported noq type now comes from moq-noq, so a consumer that also depends on upstream noq (or on iroh) sees two distinct type families. Release as web-transport-noq 0.4.0.

Blocked on moq-noq 1.3.0 reaching crates.io (moq-dev/noq#1). Verified locally against the fork checkout with a temporary path patch: cargo check --all-targets and cargo test -p web-transport-noq pass, and cargo tree shows only the moq-noq* stack.

(Written by Claude Opus 5)

🤖 Generated with Claude Code

The `noq` dependency now resolves to the `moq-noq` package, so the
re-exported `web_transport_noq::noq` types come from the fork. Import paths
are unchanged.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kixelated

Copy link
Copy Markdown
Collaborator Author

Superseded by moq-dev/noq#2: the fork ships its own adapter, web-transport-moq, and web-transport-noq stays on upstream noq.

(Written by Claude Opus 5)

@kixelated kixelated closed this Sep 21, 2026
@kixelated
kixelated deleted the moq-noq branch September 21, 2026 23:55
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