rsample
tidymodels' resampling package is retiring its old splitters for sliding windows.
A side-by-side editorial comparison of LangGraph and parsnip — release velocity, themes, recent moves, and the top alternatives to consider.
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.
parsnip added a whole new regression type, then wired R models to JAX and PyTorch
The package is expanding what tidymodels can express. Version 1.5.0 introduced ordinal_reg() as a new model type with three engines and its own link parameters, and added xgboost and qrnn engines for quantile regression. Version 1.6.0 followed with a keras3 engine for four model types, reaching Keras v3's TensorFlow, JAX and PyTorch backends. Around those, releases have been tuning-parameter range adjustments and engine-specific fixes.
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.
The package is expanding what tidymodels can express. Version 1.5.0 introduced ordinal_reg() as a new model type with three engines and its own link parameters, and added xgboost and qrnn engines for quantile regression. Version 1.6.0 followed with a keras3 engine for four model types, reaching Keras v3's TensorFlow, JAX and PyTorch backends. Around those, releases have been tuning-parameter range adjustments and engine-specific fixes.
Growth is happening on two axes: new modelling tasks that previously had no unified interface, and new engines behind tasks that already did. Both push in the same direction - a modeller specifies the model once and swaps the computational backend underneath, which is the whole premise parsnip is built on. The defunct surv_reg() shows old spellings being retired as that surface settles.
Expect further engines behind ordinal_reg() and quantile regression now that both have a home, and continued retirement of deprecated function names. The keras3 engine's multi-backend design is the obvious candidate to spread to more model types.
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 LangGraph or parsnip.
tidymodels' resampling package is retiring its old splitters for sliding windows.
tidymodels' preprocessing engine learned sparsity, then settled into deprecations.
The resampling companion to scikit-learn now ships mostly to stay compatible with it.
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 LangGraph alternatives → · See all parsnip 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 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.
Top parsnip alternatives in ai-assistants are ranked by recent ship velocity. Browse the "parsnip alternatives" section above for the current picks, or visit /alternatives/parsnip for the full list with editorial commentary on each.