Roll out running-process 4.0.0 to all dependent repos
4.0.0 is published on PyPI, crates.io, and GitHub Releases. This issue tracks the rollout into every known downstream consumer so we leave nothing on a frozen 3.x.
Why a meta issue
The Rust crate rename (running-process-core → running-process) means downstream Rust crates won't get any 3.x updates anymore. Python consumers are unaffected at the API level but should still bump their floor. We want a single place to see whether every consumer has moved.
Execution protocol (per-repo sub-agent loop)
For each repo below:
- Spawn a sub-agent with the linked sub-issue as its task.
- Clone, branch, apply migration. The migration table is in the 4.0.0 changelog.
- Local test. Run the repo's own test suite. If green → push PR. If red → analyze.
- Fix-and-retry loop. If the failure is in the consumer (stale import, wrong feature flag, API misuse), fix and retest. If green → push PR.
- Upstream-fix escalation. If the failure is genuinely a regression in
running-process 4.0.0:
- Reproduce minimally
- Fix it in this repo
- Add a unit test that locks the behavior in
- Bump the patch version (4.0.1, 4.0.2, …)
- Cut a release (the Auto Release workflow handles this once the version line in
pyproject.toml / Cargo.toml is bumped)
- Update the consumer's pin to the new patch version
- Continue the consumer's PR
- Land the consumer PR. Same gates as
clud-pr-merge: green CI, no regressions vs. that repo's main, no unresolved review comments. Squash-merge + delete branch.
Sub-issues
Rust consumers (crate rename — true breaking change)
Python consumers (ABI unchanged — pin bump + verification)
Out of scope
zackees/rclone-api, zackees/static-npm, zackees/python-rust-build-chain, zackees/self, zackees/clud/ci/banned_imports.py — only doc/code mentions, no declared dependency.crates/test-watchdog, testbins/* — internal-only, publish = false.
Done when
Every checkbox above ticks and the corresponding consumer is merged onto 4.x at its main branch.
Roll out running-process 4.0.0 to all dependent repos
4.0.0 is published on PyPI, crates.io, and GitHub Releases. This issue tracks the rollout into every known downstream consumer so we leave nothing on a frozen 3.x.
Why a meta issue
The Rust crate rename (
running-process-core→running-process) means downstream Rust crates won't get any 3.x updates anymore. Python consumers are unaffected at the API level but should still bump their floor. We want a single place to see whether every consumer has moved.Execution protocol (per-repo sub-agent loop)
For each repo below:
running-process4.0.0:pyproject.toml/Cargo.tomlis bumped)clud-pr-merge: green CI, no regressions vs. that repo'smain, no unresolved review comments. Squash-merge + delete branch.Sub-issues
Rust consumers (crate rename — true breaking change)
running-process-core = "3.4.1"— deps: upgrade running-process-core 3.4.1 → running-process 4.0.0 (crate consolidated) clud#157running-process-core = "3.1.0"— deps: upgrade running-process-core 3.1.0 → running-process 4.0.0 (crate consolidated) fastled-wasm#102running-process-core = "3.3"— deps: upgrade running-process-core 3.3 → running-process 4.0.0 (crate consolidated) zccache#387running-process-core = "3.4"— deps: upgrade running-process-core 3.4 → running-process 4.0.0 (crate consolidated) FastLED/fbuild#271Python consumers (ABI unchanged — pin bump + verification)
running-process>=3.0.8— deps: bump running-process pin to 4.0.0 codeup#1running-process>=3.4.1— deps: bump running-process pin to 4.0.0 FastLED/FastLED#2505Out of scope
zackees/rclone-api,zackees/static-npm,zackees/python-rust-build-chain,zackees/self,zackees/clud/ci/banned_imports.py— only doc/code mentions, no declared dependency.crates/test-watchdog,testbins/*— internal-only,publish = false.Done when
Every checkbox above ticks and the corresponding consumer is merged onto 4.x at its main branch.