Repository navigation
docs: drop v4-only changes from the v3 upgrading guide - #4168
Merged
Merged
Conversation
B4nan
added
adhoc
barjin
approved these changes
Sep 29, 2026
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.
The upgrading guide compares v3 to v4, but some entries described changes to APIs that only existed during v4 development, so v3 users never had them. This drops them:
navigationHooksTimeoutSecs,CachedIdClient._cachedId,_connectToRemoteBrowser/_remoteToken,IResponseWithUrl, theStatisticsstate hooks, theCreate*BackendOptionsaliases,AutoscaledPoolPredicateOptions, the@crawlee/corere-export of/internalhelpers, and the v4-only entries in the core to basic move list. I checked each one againstorigin/3.x.Follow-up to #4060, which does the same for the entries it adds.