search

tweedegolf / drive-rs

https://tweedegolf.github.io/drive-rs/
6 stars 0 forks source link

Bump the backend-dependencies group with 3 updates #46

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Bumps the backend-dependencies group with 3 updates: anyhow, schemars and serde.

Updates anyhow from 1.0.86 to 1.0.88

Release notes

Sourced from anyhow's releases.

1.0.88

  • Documentation improvements

1.0.87

  • Support more APIs, including Error::new and Error::chain, in no-std mode on Rust 1.81+ (#383)
Commits
  • 139f266 Release 1.0.88
  • aa3ab2b Merge pull request #385 from dtolnay/docnostd
  • 44c3767 Update documentation on no-std error type conversions
  • afe93e7 Release 1.0.87
  • d58fa4b Fix outdated html_root_url
  • c18d807 Disable unused doc_cfg feature
  • 8ecfcdf Merge pull request #383 from dtolnay/nostd
  • bee814a Support error sources in no-std on Rust 1.81+
  • 1eabf69 Merge pull request #382 from dtolnay/corerequest
  • 3e70139 Access generic_member_access APIs through core
  • Additional commits viewable in compare view


Updates schemars from 1.0.0-alpha.14 to 1.0.0-alpha.15

Release notes

Sourced from schemars's releases.

v1.0.0-alpha.15

Added

  • SchemaSettings now has a contract field which determines whether the generated schemas describe how types are serialized or deserialized. By default, this is set to Deserialize, as this more closely matches the behaviour of previous versions - you can change this to Serialize to instead generate schemas describing the type's serialization behaviour (GREsau/schemars#48 / GREsau/schemars#335)

Changed

  • Schemas generated for enums with no variants will now generate false (or equivalently {"not":{}}), instead of {"enum":[]}. This is so generated schemas no longer violate the JSON Schema spec's recommendation that a schema's enum array "SHOULD have at least one element".
Changelog

Sourced from schemars's changelog.

[1.0.0-alpha.15] - 2024-09-05

Added

  • SchemaSettings now has a contract field which determines whether the generated schemas describe how types are serialized or deserialized. By default, this is set to Deserialize, as this more closely matches the behaviour of previous versions - you can change this to Serialize to instead generate schemas describing the type's serialization behaviour (GREsau/schemars#48 / GREsau/schemars#335)

Changed

  • Schemas generated for enums with no variants will now generate false (or equivalently {"not":{}}), instead of {"enum":[]}. This is so generated schemas no longer violate the JSON Schema spec's recommendation that a schema's enum array "SHOULD have at least one element".
Commits
  • 4a526ad 1.0.0-alpha.15
  • 05325d2 Add Contract for generating separate serialize/deserialize schemas (#335)
  • 497333e Replace placeholder error message
  • 5d58a4d Wrap comment lines at 100 chars
  • 0672c86 Add Schema methods insert, get and remove
  • d6c8b6b Fix ui tests in nightly
  • dffa33f Enable all crate features with rust-analyzer
  • 9bba818 Move private crate exports into _private module
  • See full diff in compare view


Updates serde from 1.0.209 to 1.0.210

Release notes

Sourced from serde's releases.

v1.0.210

  • Support serializing and deserializing IpAddr and SocketAddr in no-std mode on Rust 1.77+ (#2816, thanks @​MathiasKoch)
  • Make serde::ser::StdError and serde::de::StdError equivalent to core::error::Error on Rust 1.81+ (#2818)
Commits
  • 89c4b02 Release 1.0.210
  • eeb8e44 Merge pull request #2818 from dtolnay/coreerror
  • 785c2d9 Stabilize no-std StdError trait
  • d549f04 Reformat parse_ip_impl definition and calls
  • 4c0dd63 Delete attr support from core::net deserialization macros
  • 26fb134 Relocate cfg attrs out of parse_ip_impl and parse_socket_impl
  • 07e614b Merge pull request #2817 from dtolnay/corenet
  • b1f899f Delete doc(cfg) attribute from impls that are supported in no-std
  • b4f860e Merge pull request #2816 from MathiasKoch/chore/core-net
  • d940fe1 Reuse existing Buf wrapper as replacement for std::io::Write
  • 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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions