chore(deps): Bump rustls-native-certs from 0.7.0 to 0.8.0

[dependabot]

Bumps rustls-native-certs from 0.7.0 to 0.8.0.

Release notes

Sourced from rustls-native-certs's releases.

v/0.8.0

Breaking changes

• load_native_certs() now returns a CertificateResult value containing all the certificates that were successfully found as well as any errors encountered. Changes made in 0.7.1 in order to find certificates in more locations resulted in new errors in scenarios that previously worked for most users. This change allows callers to determine the error handling strategy most appropriate to their application.

What's Changed

• Yield all the errors by @​djc in rustls/rustls-native-certs#128

0.7.3

Release notes

• If loading certificates from a directory fails, only raise that error if no certificates were successfully loaded from a file. See #124.

  In 0.8.0 we plan to alter the API to give the caller full error details, so they can choose the level of success they require; see #128.

What's Changed

• Prefer partial success to failure by @​ctz in rustls/rustls-native-certs#126

Full Changelog: rustls/rustls-native-certs@v/0.7.2...v/0.7.3

0.7.2

• Improve error reporting if we fail when loading certificates from the filesystem.

What's Changed

• rust: update semver-compatible dependencies by @​djc in rustls/rustls-native-certs#114
• Bump rustls-webpki from 0.102.4 to 0.102.5 in the crates-io group by @​dependabot in rustls/rustls-native-certs#115
• lib: add more error context when loading fails by @​cpu in rustls/rustls-native-certs#117
• Bump the crates-io group across 1 directory with 3 updates by @​dependabot in rustls/rustls-native-certs#119
• Separate online smoke tests from main CI by @​cpu in rustls/rustls-native-certs#120
• Bump the crates-io group with 2 updates by @​dependabot in rustls/rustls-native-certs#121
• Prepare 0.7.2 by @​ctz in rustls/rustls-native-certs#125

Full Changelog: rustls/rustls-native-certs@v/0.7.1...v/0.7.2

0.7.1

Notable changes

• Include certificates from the SSL_CERT_DIR environment variable and openssl-probe ProbeResult::cert_dir in the set of returned certificates. This should improve results on FreeBSD (in case the ca_root_nss package is not installed).

What's changed

• Update ring & untrusted by @​serprex in rustls/rustls-native-certs#88
• Bump rustls-pemfile from 2.0.0 to 2.1.2 by @​dependabot in rustls/rustls-native-certs#93
• Bump webpki-roots from 0.26.0 to 0.26.1 by @​dependabot in rustls/rustls-native-certs#94
• Bump x509-parser from 0.15.1 to 0.16.0 by @​dependabot in rustls/rustls-native-certs#95
• Bump security-framework from 2.9.2 to 2.10.0 by @​dependabot in rustls/rustls-native-certs#96
• Bump ring from 0.17.7 to 0.17.8 by @​dependabot in rustls/rustls-native-certs#98
• Bump rustls-webpki from 0.102.0 to 0.102.2 by @​dependabot in rustls/rustls-native-certs#99
• Bump serial_test from 2.0.0 to 3.1.0 by @​dependabot in rustls/rustls-native-certs#100

... (truncated)

Commits

• 0c2305c Bump version to 0.8.0 for incompatible changes
• 8aa350a Return all errors to caller
• cc1222a windows: reorder items
• a370164 windows: import types directly
• 202aee2 Organize imports in StdExternalCrate order
• 290bdac Apply clippy suggestions for test targets
• 0d6fb06 Prepare 0.7.3
• 7ada714 Prefer partial success to failure
• 9832a72 Adjust error wording when loading missing files
• 98612b4 Prepare 0.7.2
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9425213	Triggered	Generic Password	c74aee5	e2e_test/source_legacy/tvf/postgres_query.slt	View secret
9425213	Triggered	Generic Password	c74aee5	e2e_test/source_legacy/tvf/postgres_query.slt	View secret
9425213	Triggered	Generic Password	c74aee5	ci/scripts/e2e-source-test.sh	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[xxchan]

@dependabot recreate