Part of the design for the patched and deprecatePatch APIs included a method for users to verify when old code branches can be removed and when deprecated patches can be removed from workflow code.
It's safe to remove patches once there are only workflow histories that include the deprecated version of a patch.
Core adds the TemporalChangeVersion search attribute when emitting a patch marker but does not add information on the deprecation status of that patch.
Users can get around it by fetching all workflow histories and inspecting the patch markers but that's far from optimal.
Describe the solution you'd like
Have some method to distinguish between deprecated and non deprecated patches via visibility queries.
Part of the design for the
patchedanddeprecatePatchAPIs included a method for users to verify when old code branches can be removed and when deprecated patches can be removed from workflow code.It's safe to remove patches once there are only workflow histories that include the deprecated version of a patch. Core adds the TemporalChangeVersion search attribute when emitting a patch marker but does not add information on the deprecation status of that patch. Users can get around it by fetching all workflow histories and inspecting the patch markers but that's far from optimal.
Describe the solution you'd like
Have some method to distinguish between deprecated and non deprecated patches via visibility queries.