fix: publish ts_netmon crate so the workspace release completes

[GeiserX]

Problem (broken v0.40.0 release)

The v0.40.0 publish to crates.io failed partway — ts_control, ts_netcheck, ts_derp, … published at 0.40.0, then geiserx_ts_runtime failed:

error: failed to prepare local package for uploading
Caused by: no matching package named `geiserx_ts_netmon` found
required by package `geiserx_ts_runtime v0.40.0`

Root cause: the new ts_netmon crate (added with the opt-in network-monitor feature in #261) is a workspace member and a ts_runtime dependency, but was never added to the leaf-first publish list in scripts/publish-crates.sh. So it was never uploaded, and ts_runtime couldn't be verified against the crates.io index.

Fix

• Add geiserx_ts_netmon to the publish order in scripts/publish-crates.sh, before geiserx_ts_runtime (its only dependent). It's a true leaf (deps: tokio + tracing only), so ordering is otherwise unconstrained. Bump the crate-count references 43 → 44.
• Regenerate Cargo.lock to 0.40.0 — it lagged at 0.39.0 after the release version bump (a --locked build would reject it).

After merge

Re-dispatch the Release workflow for v0.40.0. The publish script runs with SKIP_PUBLISHED=1, so it resumes past the already-published crates and uploads ts_netmon + ts_runtime + the facade + bindings — completing the release.

No code change; release infrastructure only.

Signed-off-by: Sergio sergio@geiser.cloud

Created using Claude Code (Opus 4.8)

[coderabbitai]

Warning

Review limit reached

@GeiserX, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 7 minutes and 30 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 0f3ef629-0c62-4863-80c6-4d880f5b888c

📥 Commits

Reviewing files that changed from the base of the PR and between fe86ca0 and a6b2098.

⛔ Files ignored due to path filters (1)

• Cargo.lock is excluded by !**/*.lock, !**/Cargo.lock

📒 Files selected for processing (2)

• .github/workflows/release.yml
• scripts/publish-crates.sh

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/release-publish-ts-netmon

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}