fix(deps): update rust crate remi-s3 to 0.8.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
remi-s3	dependencies	minor	0.7.1 -> 0.8.0

---

Release Notes

Noelware/remi-rs (remi-s3)

v0.8.0

Compare Source

[!IMPORTANT]
MSRV was bumped up from v1.74.0 to v1.75 and higher on all crates

➕ Additions

• [remi-azure][remi-azure]: Allow uploading metadata into a blob when using StorageService#upload (@​auguwu)

😱 Breaking Changes

• [remi-fs][remi-fs]: Return [Cow<'static, str>][Cow<'static, str>] in [ContentTypeResolver][ContentTypeResolver] trait to prevent un-needed allocations on static strings (@​auguwu)
• [remi][remi]: All methods in StorageService require Self: Sized.

😔 Deprecations

• [remi][remi] (scheduled removal in release v0.9.0): StorageService::NAME is deprecated in this release and will be replaced by StorageService::name to allow StorageService to be a object-safe trait.

🐛 Fixes

• [remi-azure][remi-azure]: sanitize ~/ and ./ paths (@​auguwu)
• [remi-azure][remi-azure]: ensure that blob exists, otherwise, Ok(None) is returned in remi_azure::StorageService::blob (@​auguwu)
• [remi-gridfs][remi-gridfs]: fix content type detection (@​auguwu)
• [remi-gridfs][remi-gridfs]: ensure that contentType metadata field is avaliable if provided in remi::StorageService::upload (@​auguwu)
• [remi-fs][remi-fs]: fix implementations of default_resolver when using serde_json & serde_yaml features (@​auguwu)
• [remi-fs][remi-fs]: in serde_json/serde_yaml usage, return text/plain on non JSON objects/arrays & non YAML mapping/sequences (@​auguwu)
• [remi-fs][remi-fs]: allow overwriting a file's contents when uploading, otherwise, the file is atomically created (@​auguwu)

🔒 Dependency Updates

Kind	Dependency	From	To	By
Rust crate	[aws-smithy-runtime-api][aws-smithy-runtime-api]	v1.4.0	v1.5.0	@​renovate-bot in #​151
Rust crate	[serde][serde]	v1.0.199	v1.0.200	@​renovate-bot in #​152
Rust crate	[aws-sdk-s3][aws-sdk-s3]	v1.2.1	v1.3.0	@​renovate-bot in #​153
Rust crate	[aws-config][aws-config]	v1.24.0	v1.25.0	@​renovate-bot in #​153
Rust crate	[tokio-util][tokio-util]	v0.7.10	v0.7.11	@​renovate-bot in #​154
Rust crate	[file-format][file-format]	v0.24.0	v0.25.0	@​renovate-bot in #​155

Full Changelog: Noelware/remi-rs@0.7.1...0.8.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package [email protected] --precise 0.8.0
    Updating crates.io index
error: failed to select a version for the requirement `remi-s3 = "^0.7.0"`
candidate versions found which didn't match: 0.8.0
location searched: crates.io index
required by package `noelware-remi v0.1.0 (https://github.com/Noelware/core-rs?rev=e5802ca9c317431e667542d4b63d508685edae0d#e5802ca9)`
    ... which satisfies git dependency `noelware-remi` (locked to 0.1.0) of package `hazel v2.0.0 (/tmp/renovate/repos/github/Noelware/hazel)`
perhaps a crate was updated and forgotten to be re-vendored?