`CronClient.update` / `SyncCronClient.update` stripped all `None`-valued
fields from the PATCH body, so `update(end_time=None)` could never clear
a previously set cron end time. This routes an explicit `None` through
as `end_time: null` (via the existing `NOT_PROVIDED` sentinel), while an
omitted argument still leaves the value unchanged.
Verified with `make format`, `make lint`, and `make test` in
`libs/sdk-py` (493 passed), including two new tests asserting the PATCH
body carries an explicit null `end_time`.
## Description
Mirrors a server-side change by accepting an optional \`metadata\`
filter on \`crons.search\` and \`crons.count\` in both the async and
sync Python SDK clients. Matches the existing pattern used for
assistants/threads search.
## Release Note
Python SDK: \`crons.search\` and \`crons.count\` now accept an optional
\`metadata\` filter that is forwarded to the server.
## Test Plan
- [ ] New unit tests in \`tests/test_crons_client.py\` verify metadata
is forwarded for both async and sync clients and omitted when not
provided.
---------
Co-authored-by: open-swe[bot] <open-swe@users.noreply.github.com>
Co-authored-by: Parker J. Rule <pjrule@users.noreply.github.com>
**Description:** The crons create endpoint supports an end-time field
that is not currently supported in the client. Adding that parameter
here.
**Issue:** N/A
**Dependencies:** N/A
**Twitter handle:** N/A
