Files
james.maesandClaude Opus 5.5 e9fd0cef4c fix: presign row limits are a cached lower cap, no config mutation; setup card reads runtime config; empty rollback
- effective limit is min(code, row); row 0/null/higher is ignored; config never mutated
- applied to presignGet/Put/Post, previewUrl and the download-link action; row read cached 15 s
- Setup card takes connections and buckets from the runtime config and counts rules as system
- seed changeset rollback is empty; test that a host rule survives rollback
- host help kept test, stand-in marker prose in the bundle

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 17:10:53 -05:00

949 B

Upgrading

Unreleased

  • Nothing is required. Help and the Setup card appear when the qbit is produced; the schema is unchanged.
  • Optional: include db/liquibase/qbit-object-storage/object-storage-defaults.changelog.sql after the changesets that create the tables, to get a disabled generic header rule (default-mutable). It is insert-only and changes no behavior until you enable the rule.
  • Behavior change: the presign limits on an object_storage_bucket row (maxPresignGetSeconds, maxPresignPutSeconds) are now read, as a lower cap only. Any bucket row whose presign values are lower than your code config shortens links after this upgrade (the config sync copied the code values into the row on first start, so a row someone lowered earlier counts). Check the values on your bucket rows; 0 or empty means no row limit, and a value above the code limit has no effect.
  • object_storage_object_version stays empty: it is reserved.