Bump aws-smithy-http from 0.56.1 to 0.60.11 · bazeltools/bazelfe@ee748f2

The job was canceled because "macos-latest" failed.

bzl-remote-core/src/storage_backend/cloud_backend/s3.rs#L4

failed to resolve: could not find `byte_stream` in `aws_smithy_http`

bzl-remote-core/src/storage_backend/cloud_backend/s3.rs#L173

`?` couldn't convert the error to `StorageBackendError`

bzl-remote-core/src/storage_backend/cloud_backend/s3.rs#L138

`?` couldn't convert the error to `StorageBackendError`

bzl-remote-core/src/storage_backend/cloud_backend/s3.rs#L97

`?` couldn't convert the error to `StorageBackendError`

The operation was canceled.

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`

/home/runner/work/bazelfe/bazelfe/bazelfe-bazel-wrapper/Cargo.toml: `default_features` is deprecated in favor of `default-features` and will not work in the 2024 edition

/home/runner/work/bazelfe/bazelfe/bazelfe-core/Cargo.toml: `default_features` is deprecated in favor of `default-features` and will not work in the 2024 edition

bzl-remote-core/src/storage_backend/cloud_backend/mod.rs#L144

this function depends on never type fallback being `()`

bzl-remote-core/src/storage_backend/cloud_backend/mod.rs#L187

this function depends on never type fallback being `()`

bzl-remote-core/src/storage_backend/cloud_backend/mod.rs#L204

this function depends on never type fallback being `()`

bzl-remote-core/src/storage_backend/cloud_backend/mod.rs#L373

this function depends on never type fallback being `()`

`bzl-remote-core` (lib) generated 4 warnings