rsample
tidymodels' resampling package is retiring its old splitters for sliding windows.
A side-by-side editorial comparison of imbalanced-learn and LangGraph — release velocity, themes, recent moves, and the top alternatives to consider.
The resampling companion to scikit-learn now ships mostly to stay compatible with it.
imbalanced-learn is at 0.14.2. Four of the six releases in the window exist to track a scikit-learn version — 1.5, 1.7, 1.8 and 1.9 in turn — or NumPy 2.0. The genuine additions are thin: InstanceHardnessCV in 0.14.0 and a clearer SMOTENC error when the categorical encoder collapses categories.
A checkpoint-persistence maintenance train, with the tracing API still being argued over.
The feed carries the LangGraph monorepo's per-package release tags — the core library, the CLI, and three checkpoint backends — each publishing a raw commit list under a version-only title. Nearly all recent movement sits in checkpoint persistence: delta-channel history correctness, namespace matching scoped to segment boundaries, and an opt-in flag to skip expired rows on read. The core library's own changes are dependency bumps plus a tracing API that has been exposed, stripped of tags, deleted, and exposed again across three releases.
imbalanced-learn is at 0.14.2. Four of the six releases in the window exist to track a scikit-learn version — 1.5, 1.7, 1.8 and 1.9 in turn — or NumPy 2.0. The genuine additions are thin: InstanceHardnessCV in 0.14.0 and a clearer SMOTENC error when the categorical encoder collapses categories.
The project has settled into the role of a compatibility shim with a stable sampler catalogue. Release timing is set by upstream scikit-learn, not by its own roadmap, and the deprecations queued in 0.13.0 show the surface narrowing rather than growing.
The pattern points to the next release being another scikit-learn compatibility bump, with the Pipeline check_is_fitted deprecation scheduled to become an error in 0.15.
The feed carries the LangGraph monorepo's per-package release tags — the core library, the CLI, and three checkpoint backends — each publishing a raw commit list under a version-only title. Nearly all recent movement sits in checkpoint persistence: delta-channel history correctness, namespace matching scoped to segment boundaries, and an opt-in flag to skip expired rows on read. The core library's own changes are dependency bumps plus a tracing API that has been exposed, stripped of tags, deleted, and exposed again across three releases.
Checkpointing — how agent state is persisted and replayed — is where the engineering attention is concentrated, and the specific fixes are the kind that only surface once people run long-lived graphs against real databases rather than in notebooks. The second thread is that TracePolicy has not settled: added to add_node, then narrowed, then reverted outright, then re-exposed in the newest release, which puts the observability surface visibly still in design. Neither thread changes what LangGraph is for; both are the work of making a 1.x framework survive production use.
The checkpoint packages will most likely keep releasing in lockstep with the core library, since a single change routinely fans out across three tags. Whether trace_policy survives this time is the open question these entries do not answer.
Other ai-assistants products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either imbalanced-learn or LangGraph.
tidymodels' resampling package is retiring its old splitters for sliding windows.
tidymodels' preprocessing engine learned sparsity, then settled into deprecations.
parsnip added a whole new regression type, then wired R models to JAX and PyTorch
mlr3 is hardening the seams where its abstractions meet real learners
Mem0 splits agent memory from user memory, then spends a week hardening the plumbing
Every post is a comparison page, and Pictory is always the answer.
See all imbalanced-learn alternatives → · See all LangGraph alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. LangGraph is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. LangGraph is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other ai-assistants products to evaluate alongside.
Top imbalanced-learn alternatives in ai-assistants are ranked by recent ship velocity. Browse the "imbalanced-learn alternatives" section above for the current picks, or visit /alternatives/imbalanced-learn for the full list with editorial commentary on each.
Top LangGraph alternatives in ai-assistants are ranked by recent ship velocity. Browse the "LangGraph alternatives" section above for the current picks, or visit /alternatives/langgraph for the full list with editorial commentary on each.