Repository navigation
chore(quest): plan the gate hang and release version automation #7020
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,20 @@ | ||
| # [S] Nightly's gate stops hanging | ||
|
|
||
| ## Goal | ||
|
|
||
| Nightly's `just gate` step finishes instead of hanging until the job timeout, | ||
| and when a test does hang, the log names the module that hung. | ||
|
|
||
| ## Plan | ||
|
|
||
| [Run 40506938673](https://github.com/moq-dev/moq/actions/runs/40506938673/job/122198526371) | ||
| on 2026-10-27 printed nothing for its last 36 minutes before the 60-minute | ||
| timeout. Tooling-test output is buffered, so the hung module is not visible. | ||
| Found while landing [moq-dev/moq#6991](https://github.com/moq-dev/moq/pull/6991). | ||
|
|
||
| Decided 2026-10-28 (maintainer): one quest for both the fix and the | ||
| visibility. Reproduce with `just gate`, fix the hung test at its cause (never | ||
| a raised timeout), and make the gate's test output identify each module as it | ||
| runs (unbuffered or per-module timestamps) so the next hang names itself. | ||
|
|
||
| Public API: none. Wire: none. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,34 @@ | ||
| # [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 | ||
|
Comment on lines
+25
to
+27
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||
| workflows. Prefer an existing maintained tool if one covers these | ||
| ecosystems; extending release-plz's own PR is also fine. | ||
|
Comment on lines
+24
to
+29
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||
| - 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. | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Script executed:
Repository: moq-dev/moq
Length of output: 2483
Script executed:
Repository: moq-dev/moq
Length of output: 3681
Define a Go-specific release rule.
The plan includes Go in “every hand-versioned package” and says the bot “patch-bumps every package.” This conflicts with
CONTRIBUTING.md, which reservesgo/wrapper/VERSIONfor human-ownedMAJOR.MINORchanges and derives the patch in CI.Suggested plan update