Bump serde from 1.0.88 to 1.0.166

[dependabot[bot]]

Bumps serde from 1.0.88 to 1.0.166.

Release notes

Sourced from serde's releases.

v1.0.166

• Add no-alloc category to crates.io metadata

v1.0.165

• Fix incorrect count of fields passed to tuple deserialization methods when using serde(skip_deserializing) attributes (#2466, thanks @​Mingun)
• Fix -Zminimal-versions build

v1.0.164

• Allowed enum variants to be individually marked as untagged (#2403, thanks @​dewert99)

v1.0.163

• Eliminate build script from serde_derive crate to slightly reduce build time (#2442, thanks @​taiki-e)

v1.0.162

• Support deserializing flattened adjacently tagged enums from data formats which represent fields as bytes, such as the csv crate (#2377, thanks @​mfro)

  #[derive(Deserialize)]
  pub struct Record {
      common: u64,
      #[serde(flatten)]
      kind: Kind,
  }
  #[derive(Deserialize)]
  #[serde(tag = "kind", content = "parameter", rename_all = "lowercase")]
  enum Kind {
  Foo(u64),
  Bar(bool),
  }
  

  common,kind,parameter
  1,foo,42
  2,bar,true
  

v1.0.161

• Improve error messages produced by serde_test on test failure (#2435, thanks @​Mingun)

v1.0.160

• Make derived serializer/deserializer internals doc(hidden) (#2426, thanks @​compiler-errors)

v1.0.159

• Accept empty #[serde()] attribute (#2422)

v1.0.158

• Fix "expected serde crate attribute to be a string" error when using macro_rules metavariable inside of serde attribute: #[serde(crate = $serde_path)] (#2409)

... (truncated)

Commits

• 48479e4 Release 1.0.166
• dfaf48b Add no-std::no-alloc category
• dcbc3e0 Release 1.0.165
• 0289d31 Fix -Zminimal-versions build
• 015e397 No need for single-element vec for chaining one element
• 6a9a21f Resolve useless_conversion clippy lint in test
• 81ac54b Resolve redundant_closure_call clippy lint
• 6b4e755 Resolve explicit_iter_loop pedantic clippy lint
• b053b4f Touch up early return in Enum checks
• c0ba323 Support a manual trigger on CI workflow
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 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)

[dependabot[bot]]

Superseded by #318.