Repository navigation
chore: regenerate models with split create/update version requests - #1152
Merged
Merged
Conversation
apify-service-account
added
the
t-tooling
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1152 +/- ##
=======================================
Coverage 95.49% 95.49%
=======================================
Files 61 61
Lines 5947 5975 +28
=======================================
+ Hits 5679 5706 +27
- Misses 268 269 +1
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:
|
vdusek
approved these changes
Oct 19, 2026
vdusek
changed the title
vdusek
added a commit
that referenced
this pull request
Oct 19, 2026
Adds optional parameters that the API accepts and the JS client already exposes: - Task `create()` / `update()`: `description`, `max_total_charge_usd` - Webhook `create()` / `update()`: `description`, `should_interpolate_strings` - Schedule `create()` / `update()`: `notifications_email` (sent as `notifications.email`) - Store `list()` / `iterate()`: `include_unrunnable_actors` - Actor `create()`: `actor_permission_level` - Dataset, key-value store and request queue `update()`: `title` - Dataset: `flatten` and `view` on `iterate_items()`, `view` and `attachment` on `get_items_as_bytes()` and `stream_items()`, `item_format` on `create_items_public_url()` `notifications` and `actor_permission_level` go through the generated request models, which got these fields in #1152 (from apify/apify-docs#3087). Task input stays dict-only: the spec allows a list, but the API rejects anything other than an object. Closes: #1147 *✍️ Drafted by Claude Code*
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.
pyproject.toml.v2-2026-10-01T153946Z->v2-2026-10-08T073338Z.Important
Retitle this pull request to
fix:orfeat:when the diff is user-facing, so that it lands in the changelog and triggers a release -chore:does neither.