chore: Regenerate models from the published OpenAPI spec - #995
Closed
apify-service-account wants to merge 1 commit into
Closed
chore: Regenerate models from the published OpenAPI spec#995apify-service-account wants to merge 1 commit into
apify-service-account wants to merge 1 commit into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #995 +/- ##
==========================================
+ Coverage 94.65% 94.69% +0.04%
==========================================
Files 58 58
Lines 5259 5301 +42
==========================================
+ Hits 4978 5020 +42
Misses 281 281
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
|
new pipeline seems to be working |
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
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-07-28T083939Z- unchanged, which doesn't rule out a specification change: the published stamp can lag its content by a deploy. Only the diff tells.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.