finalize_model_tidyclust() and finalize_workflow_tidyclust() are now fully redundant — tune's own versions already support cluster_spec natively.
Specifically:
tune::finalize_model() explicitly checks inherits(x, "cluster_spec") in its guard condition, so it already handles tidyclust models.
tune::finalize_workflow() calls finalize_model() internally, so it also works with cluster specs automatically.
Steps
- Verify that
tune::finalize_model() and tune::finalize_workflow() produce identical results to the tidyclust versions for cluster_spec objects.
- Deprecate
finalize_model_tidyclust() and finalize_workflow_tidyclust() using the lifecycle package, pointing users to the tune equivalents.
- Remove the deprecated functions in a future breaking release.
Note
This is a breaking change for any users calling finalize_model_tidyclust() or finalize_workflow_tidyclust() directly. The deprecation period allows them to migrate to tune::finalize_model() and tune::finalize_workflow().
finalize_model_tidyclust()andfinalize_workflow_tidyclust()are now fully redundant — tune's own versions already supportcluster_specnatively.Specifically:
tune::finalize_model()explicitly checksinherits(x, "cluster_spec")in its guard condition, so it already handles tidyclust models.tune::finalize_workflow()callsfinalize_model()internally, so it also works with cluster specs automatically.Steps
tune::finalize_model()andtune::finalize_workflow()produce identical results to the tidyclust versions forcluster_specobjects.finalize_model_tidyclust()andfinalize_workflow_tidyclust()using the lifecycle package, pointing users to the tune equivalents.Note
This is a breaking change for any users calling
finalize_model_tidyclust()orfinalize_workflow_tidyclust()directly. The deprecation period allows them to migrate totune::finalize_model()andtune::finalize_workflow().