chore(deps): Bump async-trait from 0.1.89 to 0.1.91

[dependabot]

Bumps async-trait from 0.1.89 to 0.1.91.

Release notes

Sourced from async-trait's releases.

0.1.91

• Update to syn 3 (#299)
• Fix mutability for by-reference receivers (#301)

0.1.90

(yanked)

Commits

• d049ee0 Release 0.1.91
• 7a0961f Merge pull request #301 from dtolnay/mutability
• 740f86f Ignore mut_mut pedantic clippy lint in test
• 4699cd3 Fix mutability for by-reference receivers
• 6dd3573 Add regression test for issue 300
• 2371797 Release 0.1.90
• d03f075 Merge pull request #299 from dtolnay/syn3
• 6cf42c1 Update to syn 3
• b9daaba Ignore match_same_arms pedantic clippy lint
• aa706d1 Update actions/upload-artifact@v6 -> v7
• Additional commits viewable in compare view

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​async-trait@​0.1.91

View full report

[msalvatti]

@dependabot rebase

[dependabot]

Looks like this PR is already up-to-date with main! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[msalvatti]

Status: blocked on the supply-chain policy, not on anything wrong with this bump.

cargo deny and cargo audit pass here — no known advisory, no license or ban issue. The only failing step is cargo vet, and it is failing because the new version has no audit yet from any source this repository imports.

#117 has landed and separates the two causes that were tangled together. It refreshed supply-chain/imports.lock, which was five dependencies behind and was making every PR fail for reasons that had nothing to do with the PR, and it pinned CI to cargo vet --locked so the gate answers from what the repository recorded rather than from whatever upstream published that minute. What is left here is genuinely this bump:

$ cargo vet          # with the imports refreshed
Vetting Failed!

(the exact crate is listed in the job log)

Three ways forward, and the right one is a call for the maintainer rather than something to route around:

1. Wait. This is what just happened for anyhow, serde_json, syn and thiserror: Mozilla, Bytecode Alliance and Google published audits between 18 and 22 July, and the versions became vetted with no decision from us. There is no advisory here, so waiting costs nothing.
2. Audit the diff with cargo vet diff, and record it with cargo vet certify. Honest, and real work — the redis 1.3 → 1.5 diff alone is 2377 insertions.
3. Exempt it — record that we accept the version without auditing it. Fastest, and the only one that puts a trust claim in the repository that nobody earned.

Leaving this open rather than forcing it through: a gate that gets bypassed whenever it is inconvenient is not a gate.