diff --git a/.claude/shared b/.claude/shared index 763fb4c9865..e12b7a9dee4 160000 --- a/.claude/shared +++ b/.claude/shared @@ -1 +1 @@ -Subproject commit 763fb4c9865a0625716de8cde80d4af1b5edcef7 +Subproject commit e12b7a9dee41b1faf8b3d4344e4233d3f5311818 diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 10c8135fdb7..eed93b15321 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -57,3 +57,14 @@ For non-trivial tasks, file an issue or offer to run `/plan-quests`. Its `moq-sync` workflow merges n0-computer/noq weekly as a PR; review it like any other, and `PARENT` names the upstream commit each release includes. A carried change lists its upstream PR, or the reason it has none, in the fork PR. For an advisory against noq or Quinn, compare the pinned release's `PARENT` with the fixing upstream commit, then sync, release the fork, and bump the pin here. + +# Versions + +Releases are cut separately; bump only when asked. Each package's version lives in one place: + +- **Rust**: release-plz owns crate versions and Rust dependency requirements. +- **JavaScript**: `js/*/package.json` packages with a `scripts.release` entry (skip private ones like `@moq/clock`, `@moq/wasm`), plus the matching workspace version in `bun.lock`. +- **Python**: `py/moq-rs/pyproject.toml` only; `py/moq-ffi` follows the `moq-ffi-v*` tag and Rust crate. +- **Swift**: `swift/VERSION`. **Kotlin**: `moq.version` in `kt/gradle.properties`. **Dart**: `version` in `dart/moq/pubspec.yaml`. Their FFI counterparts track the Rust crate. +- **Go**: `go/wrapper/VERSION` holds a human-owned `MAJOR.MINOR` line; CI derives the patch, so only edit it for a breaking API. Leave the placeholder FFI version in `go.mod` alone. +- **OBS**: the plugin takes the `libmoq` crate's version (`cpp/obs/CMakeLists.txt`), so release-plz owns it. diff --git a/go/wrapper/README.md b/go/wrapper/README.md index cf241671b54..dbc9bd15b07 100644 --- a/go/wrapper/README.md +++ b/go/wrapper/README.md @@ -115,7 +115,7 @@ deliver them, and there is no stream fallback. ## Versioning -`VERSION` holds the human-owned `MAJOR.MINOR` line (the wrapper API version). Bump it in a PR when the wrapper's own API changes. The patch number is derived by CI from the existing mirror tags, so every release (whether triggered by a wrapper change or by a new `moq.dev/moq-ffi`) just takes the next patch on that line. +`VERSION` holds the human-owned `MAJOR.MINOR` line (the wrapper API version). Bump it in a PR only for a breaking change to the wrapper's own API. The patch number is derived by CI from the existing mirror tags, so every release (whether triggered by a wrapper change or by a new `moq.dev/moq-ffi`) just takes the next patch on that line. The committed `go.mod` carries a `require moq.dev/moq-ffi v0.0.0` **placeholder**. Do not "fix" it or add a `replace`: `just go check` injects a local `replace` to the freshly-generated bindings, and CI rewrites the `require` to the latest published `moq.dev/moq-ffi` at release time. Because Go resolves to the maximum version across the build graph, that `require` is a floor. Consumers always get an ffi at least as new as the wrapper was built against.