chore: prepare release 0.2.0 - #271
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
release
branch
3 times, most recently
from
September 23, 2026 07:48
e773a63 to
1515f87
Compare
github-actions
Bot
force-pushed
the
release
branch
4 times, most recently
from
September 25, 2026 09:40
370278f to
2b78fe6
Compare
github-actions
Bot
force-pushed
the
release
branch
from
September 25, 2026 09:59
2b78fe6 to
117f694
Compare
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
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.
This PR was created automatically. Merging it will finalize the changelog for 0.2.0
Breaking Changes
Features
Add log flags
-log.file.enabledand-log.stdout.enableANSIset the two log options from thecommand line, so a service manager that already captures stdout can turn off the
log file and the color codes without editing the config file. Neither default
changed.
Make redundancy configurable
sia.dataShardsandsia.parityShardsset the erasure coding scheme used foruploads, defaulting to the previous 10 of 30. An invalid combination is rejected
before s3d opens its listeners or database. Objects already stored keep their
original scheme and remain readable.
Validate X-Amz-Checksum-* request headers
PutObjectnow verifies theCRC32,CRC32C,CRC64NVME,MD5,SHA1,SHA256andSHA512checksum headers rather than storing them unchecked, andrefuses a mismatch with
BadDigest. A request naming more than one checksum isrefused with
InvalidRequest. Checksums sent as streamingX-Amz-Trailervalues are verified the same way, which they previously were not.
Fixes
Filter request headers from object metadata
Object writes now store only object metadata headers. Request control headers
such as signing, copy, tagging, ACL and encryption headers are no longer saved
as metadata or replayed on later reads, and metadata stored by earlier versions
is filtered when an object is read. A migration prunes it from the database so
a later
CopyObjectdoes not carry it forward.Content-Languageis now storedand returned with the object, which it previously was not.
Sync the upload directory after staging an object
Staged uploads were written and synced, but the directory holding them was
not, so an unclean shutdown could leave the database referencing a file that
no longer had a directory entry.