Client push should respect server's auto_validate=False setting - #133
Merged
olivhoenen merged 3 commits intoSep 30, 2026
Conversation
prasad-sawantdesai
requested review from
SimonPinches,
Yannicked,
maarten-ic and
olivhoenen
as code owners
September 18, 2026 14:53
Yannicked
approved these changes
Sep 23, 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.
/upload_optionsnow also reportsauto_validate(mirroringvalidation.auto_validatefrom server config), alongside the existingcopy_files/copy_idsflags.simulation pushnow checks that flag before running its local schemavalidation, skipping it when the server has
auto_validatedisabled.Defaults to validating (
True) when the flag is absent from the response,so behaviour against older servers without this field is unchanged.