# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [1.59.0] - 2026-07-04
### Added
- Added object annotations support.
- `--enable-sync-object-annotations`
- `--disable-check-annotation-etag`
- `--sync-latest-object-annotations`
- `--report-annotations-sync-status`
## [1.58.9] - 2026-06-27
Monthly update.
### Security
- Harden directory traversal check used when saving S3 objects to local
files: reject `.` and `..` path segments (previously only `../` and
`..\` were caught), and detect separators on both `/` and `\`. Does not
affect S3 access itself.
### Changed
- aws-sdk-s3 `v1.133.0 -> v1.137.0`
- Updated other dependencies
## [1.58.8] - 2026-05-25
Monthly update.
### Changed
- aws-sdk-s3 `v1.131.0 -> v1.133.0`
- Updated other dependencies
## [1.58.7] - 2026-05-17
### Changed
- AWS SDK for Rust does not support the new checksums XXHash64/3/128, MD5, and SHA-512, so an error check has been added
to prevent these from being specified as additional checksums. We plan to remove this restriction when AWS SDK for
Rust supports these new checksums.
## [1.58.6] - 2026-04-28
### Changed
- Removed `aarch64-pc-windows-msvc` (`windows-11-arm`) from CI build/test matrix while the release artifact for that
target stays suspended.
## [1.58.5] - 2026-04-28
### Changed
- Suspended `windows-aarch64` (`aarch64-pc-windows-msvc`) release artifact: `link.exe` keeps failing with
`LNK1322: cannot avoid potential ARM hazard (Cortex-A53 MPCore processor bug #843419)` and the workarounds tried in
1.58.1–1.58.3 have not stabilised the build. Pre-built binaries for this target will resume once a reliable fix is in
place.
- Switched the `aarch64-pc-windows-msvc` target to `lto = "thin"` with `codegen-units = 16` via target-specific
`rustflags` (no longer release-blocking, but kept to make local/CI builds for that target succeed).
## [1.58.2] - 2026-04-27
### Changed
- Added `/OPT:REF` and `/OPT:ICF` linker flags for `aarch64-pc-windows-msvc` to reduce binary size via dead code/data
elimination and identical COMDAT folding.
## [1.58.1] - 2026-04-27
### Fixed
- Reverted Windows `/STACK` size from `2097152` back to `2000000` to work around an `aarch64-pc-windows-msvc` linker
failure (`LNK1322: cannot avoid potential ARM hazard (Cortex-A53 MPCore processor bug #843419)`).
## [1.58.0] - 2026-04-27
### Added
- Added `--source-no-sign-request` flag for anonymous access to public source buckets
- Added `--tracing-stderr` flag to redirect all tracing to stderr
### Security
- Disabled default features on `aws-config` and `aws-sdk-s3` to drop the legacy `rustls` alias that pulls rustls 0.21 (
vulnerable rustls-webpki 0.101.x, RUSTSEC-2026-0098). The modern `default-https-client` feature, which uses rustls
0.23 via `aws-smithy-http-client`, is re-enabled explicitly.
### Changed
- aws-sdk-s3 `v1.127.0 -> v1.131.0`
- shadow-rs `v1.7.1 -> v2.0.0`
- tokio `v1.50.0 -> v1.52.1`
- hyper `v1.8.1 -> v1.9.0`
- fancy-regex `v0.17.0 -> v0.18.0`
- Updated dependencies
### Fixed
- Stop panicking with "failed printing to stdout: Broken pipe" when output is piped to a consumer that closes early (
e.g. `s3sync ... | wc -l` followed by Ctrl-C). Tracing writes now swallow `BrokenPipe`, and the indicator's trailing
newline no longer unwraps the write/flush result.
## [1.57.1] - 2026-03-28
### Changed
- Updated dependencies
- Switch Dockerfile builder image from `debian:trixie` with manual rustup to `rust:1-trixie`
## [1.57.0] - 2026-03-20
### Added
- Added `--lua-callback-timeout-milliseconds` option to prevent runaway Lua scripts from blocking the sync pipeline (
default: 10000ms, 0 to disable)
### Changed
- aws-sdk-s3 `v1.124.0 -> v1.127.0`
- clap `v4.5.60 -> v4.6.0`
- MSRV `1.91.0 -> 1.91.1`
- Updated deny.toml with advisories, bans, and sources sections
- Updated dependencies
## [1.56.1] - 2026-03-06
### Security
- fixed CVE-2026-3336
### Changed
- Updated dependencies
## [1.56.0] - 2026-02-27
### Changed
- aws-sdk-s3 `v1.122.0 -> v1.124.0`
- Added aarch64-pc-windows-msvc target configuration with static CRT linking
- Refactored
- Updated dependencies
- Updated docs
### Fixed
- Fixed event processing and added a statistical report condition that targets only the PIPELINE_END event.
## [1.55.1] - 2026-02-11
### Added
- Added Windows ARM64 binary build to GitHub releases
### Changed
- aws-sdk-s3 `v1.121.0 -> v1.122.0`
- Refactored
- Updated dependencies
- Updated docs
## [1.55.0] - 2026-01-31
### Added
- Added Lua 5.5 support
By default, s3sync uses Lua 5.4. If you want to use Lua 5.5, you can
modify [Cargo.toml](https://github.com/nidor1998/s3sync/blob/main/Cargo.toml) and rebuild s3sync.
The following is an example of how to build with Lua 5.5 support.
```toml
mlua = { version = "0.11.6", features = ["lua55", "async", "send", "vendored"], optional = true }
```
### Changed
- aws-sdk-s3 `v1.120.0 -> v1.121.0`
- Refactored
- Updated dependencies
- Updated docs
## [1.54.2] - 2026-01-23
### Changed
- aws-sdk-s3 `v1.119.0 -> v1.120.0`
- Updated dependencies
- Updated docs
### Security
- [RUSTSEC-2026-0002](https://rustsec.org/advisories/RUSTSEC-2026-0002)
## [1.54.1] - 2025-12-26
### Changed
- Refactored
- Change docker base image to `debian:trixie`
- Updated dependencies
- aws-sdk-s3 `v1.115.0 -> v1.119.0`
- Updated docs
## [1.54.0] - 2025-11-28
### Added
- `--if-none-match` option
### Fixed
- Transferring from S3 fails in special cases
[#167](https://github.com/nidor1998/s3sync/issues/167)
### Changed
- Refactored
- Updated dependencies
- Migrated from deprecated crc64fast-nvme to crc-fast-rust(1.6.0)
## [1.53.0] - 2025-11-01
### Changed
- Support for Windows 10 has ended
- MSRV = 1.88.0
- aws-sdk-s3 = "1.110.0"
- Suppressed warnings from a new version of clippy
- Updated dependencies
- Updated docs
- Updated help message
## [1.52.1] - 2025-10-04
### Changed
- Added Cargo examples
- aws-sdk-s3 = "1.107.0"
- Updated dependencies
- Updated docs
### Fixed
- Fixed a bug that `Pipeline::get_errors_and_consume()` does not return errors in certain cases.
## [1.52.0] - 2025-10-02
### Changed
- Added `stats_etag_mismatch`, `stats_checksum_mismatch` field to `STATS_REPORT` event data
- Added `Pipeline::get_sync_stats()` function to get the statistics of the transfer in the library
- Updated dependencies
### Fixed
- Fixed a bug that does not trigger `STATS_REPORT` event outside s3sync CLI.
## [1.51.0] - 2025-09-30
### Changed
- Added `STATS_REPORT` event to the event callback system
This event is triggered after the PIPELINE_END event. This event contains the statistics of the transfer.
- Updated dependencies
## [1.50.0] - 2025-09-29
### Changed
- Improved event callback system
Even if dry-run is enabled, SYNC_COMPLETE event will be triggered.
- Improved event data information in the event callback system
For example, SYNC_CHECKSUM_VERIFIED event now includes size, modified time, etag.
- Updated dependencies
## [1.49.0] - 2025-09-28
### Changed
- Added a single file upload functionality from local to S3
Previously, you could specify a directory path as the source to upload files from local to S3.
Now, you can upload a single file from local to S3 with `s3sync <local-file-path> s3://bucket-name/prefix/`
command.
This command uploads the specified local file to the specified S3 bucket and prefix.
The local file name is preserved in the S3 object name.
- Improved error messages when deleting objects from S3
- Updated dependencies
## [1.48.0] - 2025-09-23
### Changed
- Added `--ignore-glacier-warnings` option
Previously, when getting an object that needs to be restored from Glacier, s3sync fails with an error.
Now by default, s3sync shows a warning message and skips to transfer the object.
With this option, s3sync ignores the warning and skips to transfer the object.
- Updated dependencies
## [1.47.1] - 2025-09-20
### Changed
- Updated dependencies
- Updated docs
### Fixed
- `--server-side-copy` fails if the source object contains special
characters [#152](https://github.com/nidor1998/s3sync/issues/152)
## [1.47.0] - 2025-09-18
### Changed
- Added `--if-match` and `--copy-source-if-match` options
These options allow conditional operations based on ETag matching.
- Added `--max-delete'` option
This option is like rsync's `--max-delete` option.
- Updated dependencies
- Updated docs
## [1.46.0] - 2025-09-15
### Changed
- Added Linux musl statically linked binary build to release assets
- Added `--show-no-progress` option
- Improved debug/trace tracing messages
- Updated dependencies
- Updated docs
## [1.45.0] - 2025-09-14
### Changed
- Improved error/cancel handling
- aws-sdk-s3 = "1.105.0"
- Updated dependencies
- Updated docs
## [1.44.0] - 2025-09-12
### Changed
- Added dry_run info to an event callback
- [Breaking change] `EventManager::register_callback()` now takes the dry_run parameter
This is because the above feature requires it.
- Improved error handling in async functions
Even if an async function fails with Rust panic, s3sync can handle it as an error.
- Updated dependencies
- Updated docs
## [1.43.1] - 2025-09-11
### Changed
- Improved error handling in async functions
- Updated dependencies
- Updated docs
## [1.43.0] - 2025-09-10
### Changed
- Added proxy support
s3sync supports for proxy environment variables (`HTTP_PROXY`, `HTTPS_PROXY`, `ALL_PROXY`, `NO_PROXY`).
s3sync automatically respects these proxy environment variables.
- [Breaking change] Removed `legacy_hyper014_feature`
This feature is no longer needed because AWS SDK for Rust natively supports proxy.
- aws-sdk-s3 = "1.105.0"
- Updated dependencies
- Updated docs
## [1.42.2] - 2025-09-08
### Changed
- Updated docs
- Updated dependencies
## [1.42.1] - 2025-09-07
### Changed
- Improved tests
- Changed the coverage analysis tool used from cargo-tarpaulin (ptrace) to cargo-llvm-cov
This is because recently analysis with cargo-tarpaulin (ptrace) started to fail with this binary.
But the LLVM-based coverage result is significantly different from the ptrace-based one.
LLVM-based coverage analysis ignores some codes regardless of their execution status.
So, the coverage percentage may be lower than before.
- Updated dependencies
## [1.42.0] - 2025-09-04
### Changed
- Added `--disable-additional-checksum-verify` option
This option disables additional checksum verification after uploading to S3.
But the hash of the object has been stored in the metadata of the object.
- Improve dry-run logic for some S3 compatible storage
- Updated dependencies
## [1.41.0] - 2025-08-31
### Changed
- Refined release build optimization settings
Setting lto = "fat" and strip = "symbols" in Cargo.toml for `release` build.
This significantly reduces the binary size at the cost of longer build time and higher memory usage during CLI binary
release build.
And stripping symbols may make CLI binary debugging more difficult. (rarely needed)
- Updated dependencies
## [1.40.1] - 2025-08-30
### Changed
- Updated dependencies
- aws-sdk-s3 = "1.104.0"
### Fixed
- [Security] [tracing-subscriber 0.3.20](https://github.com/tokio-rs/tracing/releases/tag/tracing-subscriber-0.3.20)
ANSI Escape Sequence Injection (CVE-2025-58160)
## [1.40.0] - 2025-08-27
### Changed
- [Breaking change] `--delete-excluded` option
Earlier, `--delete` option deleted objects that are not in the source, ignoring exclude filtering options.
Now, `--filter-exclude-regex` filtering option is applied to `--delete` option.
Exclude filters other than `--filter-exclude-regex` will not prevent an object from being deleted.
If you want to delete objects that are not in the source, ignoring `--filter-exclude-regex`, use `--delete-excluded`
option.
- Updated dependencies.
## [1.39.0] - 2025-08-25
### Changed
- Added `--max-parallel-listing-max-depth` option
By default, s3sync lists objects in the source and target buckets/local files in parallel up to the second level of
subdirectories or prefixes.
And deeper levels are listed without parallelization.
This is because parallel listing at deeper levels may not improve performance.
But in some cases, parallel listing at deeper levels may improve performance.
You can configure the maximum depth of parallel listing workers with `--max-parallel-listing-max-depth` option.
- Updated dependencies.
## [1.38.0] - 2025-08-24
### Changed
- Support sync summary log
At the end of the sync, s3sync logs a summary of the sync statistics.
To log the summary, use `-v` option.
```bash
$ s3sync --additional-checksum-algorithm SHA256 -v --json-tracing test_data s3://xxxxx |tail -1 |jq
{
"timestamp": "2025-08-24T08:36:35.034711Z",
"level": "INFO",
"fields": {
"message": "sync summary",
"transferred_byte": 464519168,
"transferred_byte_per_sec": 77385200,
"transferred_object": 40,
"transferred_object_per_sec": 6,
"etag_verified": 40,
"checksum_verified": 40,
"deleted": 0,
"skipped": 0,
"error": 0,
"warning": 0,
"duration_sec": 6.002687375
}
}
$
```
- Updated dependencies.
## [1.37.0] - 2025-08-24
### Changed
- Support parallel object listing
By default, s3sync lists objects in the source and target buckets/local in parallel (default 16 workers).
The parallel listing is enabled when the root has subdirectories or prefixes.
For example, if the source is `s3://bucket-name/prefix` and there are many objects under `prefix/dir1`,
`prefix/dir2`, ..., `prefix/dir16`, s3sync lists objects under these prefixes in parallel.
But If the source has only one subdirectory under `prefix/`, s3sync does not list objects in parallel.
You can configure the number of parallel listing workers with `--max-parallel-listings` option.
If set to `1`, parallel listing is disabled.
This feature can significantly improve performance with incremental transfer when there are many objects in the source
and target bucket/local.
With express one zone storage class, parallel listing may return in progress multipart upload objects.
So, parallel listing is disabled by default when the source or target bucket uses express one zone storage class.
You can enable it with `--allow-parallel-listings-in-express-one-zone` option.
When `--enable-versioning` or `--point-in-time` option is specified, parallel listing is disabled.
Note: Parallel listing may use CPU and memory.
- Updated dependencies.
### Fixed
- Fixed a bug that does not log sync complete message.
## [1.36.0] - 2025-08-17
### Changed
- Support `SYNC_WRITE` event in the event callback system.
This event is triggered when an object (or part of an object) is written to a target.
- Support `SYNC_FILTERED` event in the event callback system.
If an object is filtered out, this event is triggered. EventData.message will contain the reason for filtering.
- Updated dependencies.
## [1.35.0] - 2025-08-15
### Changed
- Support Look-around with regular expressions.
Look-around features are invaluable for filtering objects with complex patterns.
For example, `'^(?!.*&test=true).*stage=first'` can be used to filter objects that do not contain `test=true` in the
tag and contain `stage=first` in the tag.
And you can also create regular expressions that combine multiple logical conditions with look-around features.
This feature reduces the need for Lua scripts or custom callback Rust codes to filter objects with complex patterns.
Note: This feature has been implemented with [fancy-regex](https://github.com/fancy-regex/fancy-regex) crate, which
falls back to regex crate if a given regex is not `fancy`.
- Updated documentation.
- Updated dependencies.
- aws-sdk-s3 = "1.103.0"
## [1.34.1] - 2025-08-14
### Changed
- Improved x86_64 linux performance in the highly loaded environment.
- Updated documentation.
- Updated dependencies.
### Fixed
- [Security] Fixed a bug that caused the `--allow-lua-os-library` is not enough to disable command execution in a Lua
script.
Now, `--allow-lua-os-library` limits the use of
Lua [Input and Output Facilities](https://www.lua.org/manual/5.4/manual.html#6.8).
## [1.34.0] - 2025-08-13
### Changed
- [Library] Lua scripting support
You can specify Lua scripting support CLI arguments in the library.
- aws-sdk-s3 = "1.102.0"
- Updated documentation.
- Updated dependencies.
## [1.33.0] - 2025-08-12
### Changed
- Lua scripting support
You can use Lua script to implement custom filtering, event handling, preprocessing before transferring objects to
S3.
`--preprocess-callback-lua-script`, `--event-callback-lua-script`, `--filter-callback-lua-script` options are
available for this purpose.
Lua is generally recognized as a fast scripting language. Lua engine is embedded in s3sync, so you can use Lua script
without any additional dependencies.
For example, you can use Lua script to implement custom preprocessing logic, such as dynamically modifying the object
attributes(e.g., metadata, tagging) before transferring it to S3.
By default, Lua script run as safe mode, so it cannot use Lua os library functions.
If you want to allow more Lua libraries, you can use `--allow-lua-os-library`, `--allow-lua-unsafe-vm` option.
See [Lua script example](https://github.com/nidor1998/s3sync/tree/main/src/lua/script/)
- Updated dependencies.
## [1.32.0] - 2025-08-10
### Changed
- Support a user defined callback while listing the source
- Updated dependencies.
## [1.31.0] - 2025-08-08
### Changed
- Support Amazon S3 Access Points ARNs
Access Point alias is also supported (As before).
- aws-sdk-s3 = "1.101.0"
- Updated dependencies.
## [1.30.0] - 2025-08-06
### Changed
- Support user-defined event callback within s3sync CLI
If you are familiar with Rust, you can use `UserDefinedEventCallback` to implement custom event handling logic, such
as logging or monitoring and custom actions before and after synchronization.
Thanks to Rust's clear compiler error messages and robust language features, even software engineers unfamiliar with
the language can implement it easily.
To use `UserDefinedEventCallback`, you need to implement the `EventCallback` trait and rebuild the s3sync binary.
## [1.29.0] - 2025-08-04
### Changed
- Support a preprocess callback before uploading to S3 within the library
We can use this to modify the object attributes(e.g. metadata, tagging) dynamically before uploading to s3.
See [docs.rs](https://docs.rs/s3sync/latest/s3sync/) for more information.
- Updated dependencies.
## [1.28.0] - 2025-08-03
### Changed
- Support an event callback system within the library
See [docs.rs](https://docs.rs/s3sync/latest/s3sync/) for more information.
- Updated dependencies.
## [1.27.0] - 2025-07-27
### Changed
- Added Multi-Region Access Point support.
- aws-sdk-s3 = "1.100.0"
- Updated dependencies.
## [1.26.1] - 2025-07-21
### Changed
- Updated documentation.
## [1.26.0] - 2025-07-20
### Changed
- Rust Edition 2024 build
- Updated documentation.
- Updated dependencies.
## [1.25.2] - 2025-07-20
### Changed
- Updated help message.
## [1.25.1] - 2025-07-19
### Changed
- Updated documentation.
- MSRV = 1.86.0(From 1.25.0)
## [1.25.0] - 2025-07-18
### Changed
- Added `--report-sync-status` option.
- Added `--report-metadata-sync-status` option.
- Added `--report-tagging-sync-status` option.
- aws-sdk-s3 = "1.98.0"
- Updated dependencies.
## [1.24.0] - 2025-07-16
### Changed
- Added `--point-in-time` option.
- Updated dependencies.
### Fixed
- Fixed statistics issue when `--server-side-copy`.
## [1.23.0] - 2025-07-15
### Changed
- Added `--filter-include-content-type-regex` option.
- Added `--filter-exclude-content-type-regex` option.
## [1.22.1] - 2025-07-14
### Changed
- Improved a help message.
- Updated dependencies.
### Fixed
- Fixed the skip statistics issue when tag/metadata-based filtering is used.
## [1.22.0] - 2025-07-12
### Changed
- Added `--filter-include-metadata-regex` option.
- Added `--filter-exclude-metadata-regex` option.
- Added `--filter-include-tag-regex` option.
- Added `--filter-exclude-tag-regex` option.
- Added `--no-sync-system-metadata` option.
- Added `--no-sync-user-defined-metadata` option.
- Updated dependencies.
## [1.21.1] - 2025-07-12
### Changed
- Improved tests.
## [1.21.0] - 2025-07-11
### Changed
- Added `--operation-timeout-milliseconds` option.
- Added `--operation-attempt-timeout-milliseconds` option.
- Added `--connect-timeout-milliseconds` option.
- Added `--read-timeout-milliseconds` option.
- Improved socket error handling.
## [1.20.0] - 2025-07-11
### Changed
- Add help message grouping using help_heading in CLI
https://github.com/nidor1998/s3sync/issues/90
- updated dependencies.
## [1.19.0] - 2025-07-10
### Changed
- Added `--website-redirect` option.
- Improved tests.
- Refactored.
- updated dependencies.
### Fixed
- Fixed `--tagging` option bug that does not work with `--server-side-copy` option.
## [1.18.0] - 2025-07-09
### Changed
- [Breaking change] Distinct exit code for warnings. https://github.com/nidor1998/s3sync#cli-process-exit-codes
- Added `--server-side-copy` option.
- updated dependencies.
## [1.17.0] - 2025-07-06
### Changed
- Added `--check-mtime-and-etag` option.
- Added `--check-mtime-and-additional-checksum` option.
- Added `--source-request-payer`, `--target-request-payer` options.
- updated dependencies.
## [1.16.0] - 2025-07-03
### Changed
- [Breaking change]Disabled proxy support by default. https://github.com/nidor1998/s3sync/issues/78
- aws-sdk-s3 = "1.96.0"
- updated dependencies.
- MSRV = 1.85.0
### Fixed
- Fixed unnecessary etag check in dry-run mode.
## [1.15.0] - 2025-06-22
### Changed
- Added Amazon S3 Transfer Acceleration support.
## [1.14.0] - 2025-06-22
### Changed
- Multipart Upload/download large files from/to S3 in parallel
- aws-sdk-s3 = "1.93.0"
- updated dependencies.
### Fixed
- Fixed `--auto-chunksize` bug that warn E-tag mismatch.
- Fixed an issue where bandwidth restrictions did not function correctly during high loads, causing applications to
freeze.
## [1.13.4] - 2025-06-08
### Changed
- Refactored. Removed unnecessary unwrap().
- aws-sdk-s3 = "1.91.0"
- updated dependencies.
## [1.13.3] - 2025-05-28
### Changed
- Improved tests.
- Refactored
## [1.13.2] - 2025-05-26
### Changed
- aws-sdk-s3 = "1.88.0"
- Refactored
## [1.13.1] - 2025-05-21
### Fixed
- fixed exit code when s3sync fails. https://github.com/nidor1998/s3sync/issues/68
- fixed latest version of clippy warnings.
### Changed
- MSRV = 1.82.0
- aws-sdk-s3 = "1.86.0"
## [1.13.0] - 2025-04-07
### Changed
Added default additional checksum verification for Express One Zone.
see https://github.com/nidor1998/s3sync/issues/65
### Changed
- aws-sdk-s3 = "1.82.0"
## [1.12.3] - 2025-03-27
### Changed
- Improved tests.
- Refactored
## [1.12.2] - 2025-03-24
### Changed
- Improved tests.
- Refactored
## [1.12.1] - 2025-03-17
### Changed
Improved e2e test.
## [1.12.0] - 2025-03-15
### Changed
Changed to using Hyper 1.x internally, Some features are not available in Hyper 1.x, so separated as
`legacy_hyper014_feature` feature.
`--no-verify-ssl`, `--http-proxy` `--https-proxy` options require `legacy_hyper014_feature` feature.It is enabled by
default.
see https://github.com/nidor1998/s3sync/issues/59.
## [1.11.0] - 2025-03-12
### Added
Support DSSE-KMS encryption with `--sse aws:kms:dsse` option.
### Changed
- aws-sdk-s3 = "1.79.0"
## [1.10.3] - 2025-03-08
### Fixed
- Fix: `--auto-chunksize` bug. #55
### Changed
- aws-sdk-s3 = "1.76.0"
## [1.10.2] - 2025-02-14
### Changed
- Updated README.md
## [1.10.1] - 2025-02-13
### Fixed
- Fix: `--enable-additional-checksum` bug. #51
## [1.10.0] - 2025-02-10
### Added
Support CRC32/CRC32C full object checksum with `--full-object-checksum` option.
## [1.9.0] - 2025-02-07
### Added
Added `--disable-content-md5-header` option. It disables the ETag verification for the uploaded object.
### Changed
- aws-sdk-s3 = "1.74.0"
## [1.8.0] - 2025-02-05
### Added
- Added CRC64NVME checksum support.
- Currently, Only CRC64NVME checksum is supported for full object checksum.
### Changed
- aws-sdk-s3 = "1.72.0"
## [1.7.2] - 2025-01-25
### Changed
- aws-sdk-s3 = "1.71.0"
## [1.7.1] - 2024-12-25
### Fixed
- Fix conditional compilation of build script without version feature #42
## [1.7.0] - 2024-12-21
### Added
- Added disable payload signing `--disable-payload-signing` option.
### Changed
- aws-sdk-s3 = "1.66.0"
- Supported Rust Versions (MSRV) = 1.81.0
## [1.6.2] - 2024-11-23
### Changed
- aws-sdk-s3 = "1.62.0"
## [1.6.1] - 2024-09-23
### Changed
- aws-sdk-s3 = "1.51.0"
- Supported Rust Versions (MSRV) = 1.78.0
## [1.6.0] - 2024-07-20
### Fixed
- `--delete` option does not stop the pipeline after a failure
- `--disable-stalled-stream-protection` not working #32
### Changed
- aws-sdk-s3 = "1.41.0"
## [1.5.0] - 2024-06-15
### Added
- Added Additional checksum(SHA256/SHA1/CRC32/CRC32C) based incremental transfer `--check-additional-checksum` option.
- Added `get_errors_and_consume()` to `Pipeline` to get errors.
### Changed
- aws-sdk-s3 = "1.36.0"
## [1.4.0] - 2024-06-02
### Added
- Added HTTPS proxy authentication support.
- Added `--check-etag` and `--check-etag` & `--auto-chunksize` option.
### Changed
- aws-sdk-s3 = "1.32.0"
## [1.3.0] - 2024-04-28
### Added
- Added [Stalled-stream protection](https://github.com/awslabs/aws-sdk-rust/discussions/956) support(enabled by
default).
- Added Express One Zone integration tests.
### Changed
- aws-sdk-s3 = "1.24.0"
## [1.2.0] - 2024-03-28
### Added
- Added Amazon S3 Express One Zone storage class support.
### Changed
- aws-sdk-s3 = "1.21.0"
## [1.1.0] - 2023-12-25
### Fixed
- fixed `--aws-sdk-tracing` bug.
### Changed
- aws-sdk-s3 = "1.11.0"
## [1.0.0] - 2023-11-28
### Changed
- Initial release.
- aws-sdk-s3 = "1.1.0"