fix: regenerate models from the candidate OpenAPI spec - #1040
Closed
vdusek wants to merge 1 commit into
Closed
Conversation
vdusek
added
adhoc
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1040 +/- ##
=======================================
Coverage 95.27% 95.27%
=======================================
Files 59 59
Lines 5502 5502
=======================================
Hits 5242 5242
Misses 260 260
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Contributor
Author
|
closing in favor of #1041 |
vdusek
pushed a commit
that referenced
this pull request
Aug 31, 2026
…d datetime usage dates (#1041) Regenerates the models from the [published OpenAPI specification](https://docs.apify.com/api/openapi.json) (`v2-2026-08-27T071624Z` -> `v2-2026-08-30T172245Z`), which now describes the API's actual behavior after apify/apify-docs#2932. User-facing changes: - `Task.input`, `CreateTaskRequest.input`, and `UpdateTaskRequest.input` also accept a list of objects, which the API stores and returns. - `DailyServiceUsages.date` is a timezone-aware `datetime` instead of `str`. - `Run.general_access` is optional - the API omits it for a run that follows the owner's account setting. - `UserPrivateInfo.plan`, `effective_platform_features`, and `is_paying` are optional - `GET /v2/users/{userId}` responses don't carry them. Previously, responses with any of these shapes failed model validation. Closes #1040 (a manual test run of the same regeneration against a pre-merge bundle of the spec). > Generated by the [Regenerate models](https://github.com/apify/apify-client-python/actions/workflows/on_schedule_regenerate_models.yaml) workflow.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Models regenerated (
poe generate-models-from-file) from the candidate spec in apify/apify-docs#2932, which fixes the six known API/spec deviations, to test them against this repo's test suite. The changes: taskinputaccepts a list of objects,DailyServiceUsages.dateis a datetime,Run.general_accessand the private fields onUserPrivateInfoare optional.Do not merge before apify/apify-docs#2932 is deployed - the recorded spec version in
pyproject.tomldeliberately still names the published specification, and the nightly regeneration will produce this same diff once the spec is live.✍️ Drafted by Claude Code