Bump the cargo group with 8 updates

[dependabot]

Bumps the cargo group with 8 updates:

Package	From	To
parry2d-f64	0.13.5	0.13.6
parry3d-f64	0.13.5	0.13.6
bytemuck	1.14.0	1.14.1
chrono	0.4.31	0.4.33
octocrab	0.33.1	0.33.3
serde	1.0.195	1.0.196
serde_json	1.0.111	1.0.113
env_logger	0.10.2	0.11.1

Updates parry2d-f64 from 0.13.5 to 0.13.6

Changelog

Sourced from parry2d-f64's changelog.

v0.13.6

Fixed

• Fix ball-convex manifolds missing contacts in some corner cases.
• Fix panic in TriMesh::intersection_with_plane.

Commits

• e57762f Release v0.13.6
• af38912 Merge pull request #148 from Ralith/robust-ball-manifold
• ac33c4a Merge pull request #163 from robtfm/fix-voxel-dim-calc
• 01f6983 Merge pull request #161 from mockersf/panic-trimesh-intersection-plane
• 0a116a9 Merge branch 'dimforge:master' into fix-voxel-dim-calc
• 4ea142f fix voxel dim calc
• aefe2a6 Merge pull request #159 from waywardmonkeys/clippy-needless-return
• aa2ef31 Merge pull request #160 from waywardmonkeys/clippy-mem_replace_with_default
• 01d43db insert adjacencies in the correct order
• 468811b clippy: Fix mem_replace_with_default.
• Additional commits viewable in compare view

Updates parry3d-f64 from 0.13.5 to 0.13.6

Changelog

Sourced from parry3d-f64's changelog.

v0.13.6

Fixed

• Fix ball-convex manifolds missing contacts in some corner cases.
• Fix panic in TriMesh::intersection_with_plane.

Commits

• e57762f Release v0.13.6
• af38912 Merge pull request #148 from Ralith/robust-ball-manifold
• ac33c4a Merge pull request #163 from robtfm/fix-voxel-dim-calc
• 01f6983 Merge pull request #161 from mockersf/panic-trimesh-intersection-plane
• 0a116a9 Merge branch 'dimforge:master' into fix-voxel-dim-calc
• 4ea142f fix voxel dim calc
• aefe2a6 Merge pull request #159 from waywardmonkeys/clippy-needless-return
• aa2ef31 Merge pull request #160 from waywardmonkeys/clippy-mem_replace_with_default
• 01d43db insert adjacencies in the correct order
• 468811b clippy: Fix mem_replace_with_default.
• Additional commits viewable in compare view

Updates bytemuck from 1.14.0 to 1.14.1

Changelog

Sourced from bytemuck's changelog.

1.14.1

• docs clarifications.

1.14

• write_zeroes and fill_zeroes functions: Writes (to one) or fills (a slice) zero bytes to all bytes covered by the provided reference. If your type has padding, this will even zero out the padding bytes.
• align_offset feature: causes pointer alignment checks to use the align_offset pointer method rather than as-casting the pointer to usize. This may improve codegen, if the compiler would have otherwise thought that the pointer address escaped. No formal benchmarks have been done either way.
• must_cast feature: Adds must_* family of functions. These functions will fail to compile if the cast requested can't be statically known to succeed. The error messages can be kinda bad when this happens, but eliminating the possibility of a runtime error might be worth it to you.

1.13.1

• Remove the requirement for the source data type to be AnyBitPattern on pod_collect_to_vec, allowing you to pod collect vecs of char into vecs of u32, or whatever.

1.13

• Now depends on bytemuck_derive-1.4.0
• Various small enhancements that would have been patch version updates, but which have been rolled into this minor version update.

1.12.4

• This has additional impls for existing traits and cleans up some internal code, but there's no new functions so I guess it counts as just a patch release.

1.12.3

• This bugfix makes the crate do stuff with Arc or not based on the target_has_atomic config. Previously, some targets that have allocation but not atomics were getting errors. This raises the MSRV of the extern_crate_alloc feature to 1.60, but opt-in features are not considered to be hard locked to 1.34 like the basic build of the crate is.

1.12.2

• Fixes try_pod_read_unaligned bug that made it always fail unless the target type was exactly pointer sized in which case UB could happen. The CheckedBitPattern::is_valid_bit_pattern was being asked to check that a reference to the pod value was a valid bit pattern, rather than the actual bit pattern itself, and so the check could in some cases be illegally

... (truncated)

Commits

• 1e1a22e chore: Release bytemuck version 1.14.1
• 2ae1a14 changelog
• 8dc32b1 Explicitly document that pod_read_unaligned and try_pod_read_unaligned don't ...
• 085a5f5 Revise the crate-level docs.
• c705218 Added custom crate path with tests (#209)
• fd27a5b Add from_box_bytes and box_bytes_of with BoxBytes type (#211)
• d10fbfc allow deriving CheckedBitPattern for enums with fields (#171)
• See full diff in compare view

Updates chrono from 0.4.31 to 0.4.33

Release notes

Sourced from chrono's releases.

0.4.33

This release fixes the broken docrs.rs build of chrono 0.4.32.

What's Changed

• Make rkyv feature imply size_32 (#1383)
• Fixed typo in Duration::hours() exception (#1384, thanks @​danwilliams)

v0.4.32

In this release we shipped part of the effort to reduce the number of methods that could unexpectedly panic, notably for the DateTime and Duration types.

Chrono internally stores the value of a DateTime in UTC, and transparently converts it to the local value as required. For example adding a second to a DateTime needs to be done in UTC to get the correct result, but adding a day needs to be done in local time to be correct. What happens when the value is near the edge of the representable range, and the implicit conversions pushes it beyond the representable range? Many methods could panic on such inputs, including formatting the value for Debug output.

In chrono 0.4.32 the range of NaiveDate, NaiveDateTime and DateTime is made slightly smaller. This allows us to always do the implicit conversion, and in many cases return the expected result. Specifically the range is now from January 1, -262144 until December 31, 262143, one year less on both sides than before. We expect this may trip up tests if you hardcoded the MIN and MAX dates.

Duration had a similar issue. The range of this type was pretty arbitrary picked to match the range of an i64 in milliseconds. Negating an i64::MIN pushes a value out of range, and in the same way negating Duration::MIN could push it out of our defined range and cause a panic. This turns out to be somewhat common and hidden behind many layers of abstraction. We adjusted the type to have a minimum value of -Duration::MAX instead and prevent the panic case.

Other highlights:

• Duration gained new fallible initialization methods.
• Better support for rkyv.
• Most methods on NaiveDateTime are now const.
• We had to bump our MSRV to 1.61 to keep building with our dependencies. This will also allow us to make more methods on DateTime const in a future release.

Complete list of changes:

Fixes

• Fix panic in TimeZone::from_local_datetime (#1071)
• Fix out of range panics in DateTime getters and setters (#1317, #1329)

Additions

• Add NaiveDateTime::checked_(add|sub)_offset (#1313)
• Add DateTime::to_utc (#1325)
• Duration features part 1 (#1327)
• Make methods on NaiveDateTime const where possible (#1286)
• Split clock feature into clock and now (#1343, thanks @​mmastrac)
• Add From<NaiveDate> for NaiveDateTime (#1355, thanks @​dcechano)
• Add NaiveDateTime::from_timestamp_nanos (#1357, thanks @​Ali-Mirghasemi)
• Add Months::num_months() and num_years() (#1373, thanks @​danwilliams)
• Add DateTime<Utc>::from_timestamp_millis (#1374, thanks @​xmakro)

Changes

• Fix panic in Duration::MIN.abs() (adjust Duration::MIN by 1 millisecond) (#1334)
• Bump MSRV to 1.61 (#1347)
• Update windows-targets requirement from 0.48 to 0.52 (#1360)
• Update windows-bindgen to 0.52 (#1379)

Deprecations

• Deprecate standalone format functions (#1306)

Documentation

• Improve doc comment and tests for timestamp_nanos_opt (#1299, thanks @​mlegner)

... (truncated)

Commits

• 7c419a3 Prepare 0.4.33 release
• a9b37c4 Make rkyv feature default to size_32
• a73b543 Don't assume rkyv-(16|32|64) implies the rkyv feature
• b5381f8 Fixed typo in Duration::hours() exception
• bf70419 52
• 7757386 Prepare 0.4.32 release
• cee242a Fix typos in Datelike impl for DateTime
• 6ec8f97 Add from_timestamp_millis to DateTime<Utc> (#1374)
• 65f0cc2 CI Linting: Fix missing sources checkout in toml job.
• 5536687 Add Months::as_u32() (#1373)
• Additional commits viewable in compare view

Updates octocrab from 0.33.1 to 0.33.3

Release notes

Sourced from octocrab's releases.

v0.33.3

Other

• Handle redirects in ReleasesHandler::stream_asset(). (#556)
• Tests for locking and unlocking issue comments (#557)

v0.33.2

Other

• Resolving issue with deleting reactions from issues. (#555)
• Added a test for repos().is_collaborator(). The 204 case is good! (#553)

Other

• Added a test case for repos().is_collaborator() to cover both 204 and 404 cases.

Changelog

Sourced from octocrab's changelog.

0.33.3 - 2024-01-26

Other

• Handle redirects in ReleasesHandler::stream_asset(). (#556)
• Tests for locking and unlocking issue comments (#557)

0.33.2 - 2024-01-24

Other

• Resolving issue with deleting reactions from issues. (#555)
• Added a test for repos().is_collaborator(). The 204 case is good! (#553)

Other

• Added a test case for repos().is_collaborator() to cover both 204 and 404 cases.

Commits

• 7789a24 chore: release (#558)
• fbfb3a8 Handle redirects in ReleasesHandler::stream_asset(). (#556)
• d42c0a3 Tests for locking and unlocking issue comments (#557)
• 5caca08 chore: release (#554)
• c4c3a21 Resolving issue with deleting reactions from issues. (#555)
• 07e09ed Added a test for repos().is_collaborator(). The 204 case is good! (#553)
• See full diff in compare view

Updates serde from 1.0.195 to 1.0.196

Release notes

Sourced from serde's releases.

v1.0.196

• Improve formatting of "invalid type" error messages involving floats (#2682)

Commits

• ede9762 Release 1.0.196
• d438c2d Merge pull request #2682 from dtolnay/decimalpoint
• bef110b Format Unexpected::Float with decimal point
• b971ef1 Merge pull request #2681 from dtolnay/workspacedeps
• 29d9f69 Fix workspace.dependencies default-features future compat warning
• aecb408 Sort workspace dependencies
• 1c675ab Merge pull request #2678 from rodoufu/workspaceDependencies
• dd61963 Adding workspace dependencies
• 111803a Merge pull request #2673 from Sky9x/msrv-badge
• 0024f74 Use shields.io's MSRV badges
• See full diff in compare view

Updates serde_json from 1.0.111 to 1.0.113

Release notes

Sourced from serde_json's releases.

v1.0.113

• Add swap_remove and shift_remove methods on Map (#1109)

v1.0.112

• Improve formatting of "invalid type" error messages involving floats (#1107)

Commits

• 09d865b Release 1.0.113
• 5aeab4e Merge pull request #1109 from serde-rs/remove
• ca3c2ca Add swap_remove and shift_remove methods on Map
• 7fece96 Release 1.0.112
• 6a6d2bb Merge pull request #1107 from serde-rs/unexpectedfloat
• 83d7bad Format f64 in error messages using ryu
• 107c2d1 Merge pull request #1106 from serde-rs/invalidvalue
• 62ca3e4 Handle Unexpected::Unit in Error::invalid_value
• 296fafb Factor out JSON-specific Display impl for serde::de::Unexpected
• e56cc69 Merge pull request #1105 from keienWang/master
• Additional commits viewable in compare view

Updates env_logger from 0.10.2 to 0.11.1

Release notes

Sourced from env_logger's releases.

v0.11.1

What's Changed

• fix(fmt): Fix passing of WriteStyle when using Target::Pipe by @​Bobo1239 in rust-cli/env_logger#302

New Contributors

• @​Bobo1239 made their first contribution in rust-cli/env_logger#302

Full Changelog: rust-cli/env_logger@v0.11.0...v0.11.1

v0.11.0

What's Changed

• refactor(fmt): More anstream prep by @​epage in rust-cli/env_logger#297
• fix(fmt): Improve terminal styling support by @​epage in rust-cli/env_logger#298
• refactor: Split out env_filter package by @​epage in rust-cli/env_logger#299
• feat(filter): Add a Logger decorator by @​epage in rust-cli/env_logger#300

Full Changelog: rust-cli/env_logger@v0.10.2...v0.11.0

Changelog

Sourced from env_logger's changelog.

[0.11.1] - 2024-01-27

Fixes

• Allow styling with Target::Pipe

[0.11.0] - 2024-01-19

Breaking Change

• Removed bespoke styling API
  • env_logger::fmt::Formatter::style
  • env_logger::fmt::Formatter::default_styled_level
  • env_logger::fmt::Style
  • env_logger::fmt::Color
  • env_logger::fmt::StyledValue
• Removed env_logger::filter in favor of env_filter

Compatibility

MSRV changed to 1.71

Features

• Automatically adapt ANSI escape codes in logged messages to the current terminal's capabilities
• Add support for NO_COLOR and CLICOLOR_FORCE, see https://bixense.com/clicolors/

Fixes

• Print colors when is_test(true)

Commits

• 7113ad4 chore: Release
• 9f73bde docs: Update changelog
• 489ba18 Merge pull request #302 from Bobo1239/main
• 6f31706 fix(fmt): Fix passing of WriteStyle when using Target::Pipe
• 8f4361b chore: Release
• ba41ebb docs: Update changelog
• 5e226cb chore: Release
• 23441be Merge pull request #300 from epage/other
• 6c2ea80 style(filter): Clean up
• 2d35260 feat(filter): Add a Logger decorator
• 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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> 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 <dependency name> 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 <dependency name> 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 <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions