diff --git a/quest/m1/README.md b/quest/m1/README.md index 48bc378104c..a86e825a417 100644 --- a/quest/m1/README.md +++ b/quest/m1/README.md @@ -186,7 +186,6 @@ removed). - [JS SETUP rejection ownership](/quest/m1/js-setup-rejection.md) - reproduce an unhandled version-refusal rejection without weakening the refusal - [moq-clock moves into kio::clock](/quest/m1/kio-clock.md) - moq-clock and its test macro become `kio::clock` and `#[kio::test]` before the cut publishes them - [Poll-first async](/quest/m1/poll-first/README.md) - library crates compile no coroutines by default: async wrappers are generated from `poll_*` and gated behind an `async` feature -- [Every package's release backport ships](/quest/m1/release-versions.md) - a bot bumps every hand-versioned package changed on `release`, so backports publish without a manual bump ## Related diff --git a/quest/m1/release-versions.md b/quest/m1/release-versions.md deleted file mode 100644 index 7888c2d6315..00000000000 --- a/quest/m1/release-versions.md +++ /dev/null @@ -1,34 +0,0 @@ -# [M] Every package's release backport ships - -## Goal - -A fix merged into `release` for any published package publishes without a -hand-made version bump. Today release-plz bumps only Rust crates, so a -backport touching only a JS, Python, Dart, Kotlin, Swift, Go, C, or C++ -package lands on `release` unchanged in version and its release workflow -skips it as already published. - -## Plan - -Found 2026-10-28: the @moq/flate and @moq/net backports -([moq-dev/moq#6961](https://github.com/moq-dev/moq/pull/6961), -[moq-dev/moq#6959](https://github.com/moq-dev/moq/pull/6959), -[moq-dev/moq#6967](https://github.com/moq-dev/moq/pull/6967)) merged and the -release PR merged, but Release JS logged "already published, skipping" and a -separate hand bump was needed. - -Decided 2026-10-28 (maintainer): - -- Scope: every hand-versioned package listed in CONTRIBUTING.md's Versions - section, not just JS. -- Mechanism: a release-plz-like bot. On each push to `release`, it opens or - updates one PR that patch-bumps every package whose sources changed since - its last published version (with the matching lockfile entries, e.g. - `bun.lock`, `uv.lock`); merging it publishes through the existing release - workflows. Prefer an existing maintained tool if one covers these - ecosystems; extending release-plz's own PR is also fine. -- Until this lands, a backport author bumps by hand. - -Update CONTRIBUTING.md's Versions and backport bullets to describe the result. - -Public API: none. Wire: none.