You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Default 400MB max file size causes backward compatibility break when malware scanning is disabled #729
currently enforces a default maximum file size of 400MB when no max size annotation is configured.
This introduces a backward compatibility breaking change. Previously, files of any size could be uploaded successfully, for files larger than 400MB, malware scanning was skipped, but uploads were not blocked. With the current behavior, uploads larger than 400MB are rejected by default. This impacts existing consumers
Proposed fix (agreed):
Enforce the 400MB size limit only when malware scanning is enabled and Do not apply a default size restriction when malware scanning is disabled
Activity
github-actions commentedon Feb 5, 2026
👋 Hello @deepikaSingh2711, thank you for submitting this issue. Our team is reviewing your report and will follow up with you as soon as possible.
Schmarvinius commentedon Feb 5, 2026
Closing since it is a duplicate to #727
Simplify nested conditionals in ModifyAttachmentEventFactory
Simplify nested conditionals in ModifyAttachmentEventFactory