chore: sync PHP client with Apify OpenAPI spec v2-2026-08-14T072928Z - #10
Open
Pijukatel wants to merge 1 commit into
Open
chore: sync PHP client with Apify OpenAPI spec v2-2026-08-14T072928Z#10Pijukatel wants to merge 1 commit into
Pijukatel wants to merge 1 commit into
Conversation
Bumps API_SPEC_VERSION to match the live spec (apify-docs #2840, Actor task publication fields). This client already implemented isPublic/publicConfig/ TaskPublicConfig ahead of the spec (0.4.0); no client code change needed. Co-authored-by: Claude <noreply@anthropic.com>
github-actions
Bot
added
the
t-tooling
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
3 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.
Bumps
Version::API_SPEC_VERSIONto the live Apify OpenAPI specv2-2026-08-14T072928Z(apify-docs #2840, Actor task publication fields). This client already implementedTask.isPublic/publicConfig/TaskPublicConfigahead of the spec (0.4.0, PR #7) and had its docblocks corrected in PR #9; the only remaining gap was the version constant. No client code or public interface change.