chore: pin apify to 4.0.2b5 beta in Python templates - #904
Draft
vdusek wants to merge 2 commits into
Draft
Conversation
vdusek
added
t-tooling
github-actions
Bot
added
the
tested
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.
Pins
apifyto the4.0.2b5beta (exact pin — pip does not select pre-releases from a version range) in all Python templates, to run the template smoke tests against the upcoming SDK release. Covers 17requirements.txttemplates pluspython-uv(pyproject.toml+uv.lock).python-crewaiis left unchanged: it is still on SDK v3 becauselangchain-apifycapsapify-client < 3.0.0, which is incompatible with apify 4.x (requiresapify-client >= 3.1.0).Not meant to be merged as-is — testing only.
✍️ Drafted by Claude Code