Bump the all group in /local-registry with 7 updates

[dependabot]

Bumps the all group in /local-registry with 7 updates:

Package	From	To
cached	0.48.0	0.48.1
chrono	0.4.31	0.4.33
indexmap	2.1.0	2.2.1
itertools	0.12.0	0.12.1
serde	1.0.195	1.0.196
strum	0.25.0	0.26.1
strum_macros	0.25.3	0.26.1

Updates cached from 0.48.0 to 0.48.1

Changelog

Sourced from cached's changelog.

[0.48.1 / [cached_proc_macro[0.19.1]] / [cached_proc_macro_types[0.1.1]]]

Added

• Include LICENSE file in cached_proc_macro and cached_proc_macro_types

Changed

Removed

Commits

• 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 indexmap from 2.1.0 to 2.2.1

Changelog

Sourced from indexmap's changelog.

• 2.2.1

  • Corrected the signature of RawOccupiedEntryMut::into_key(self) -> &'a mut K, This a breaking change from 2.2.0, but that version was published for less than a day and has now been yanked.

• 2.2.0

  • The new IndexMap::get_index_entry method finds an entry by its index for in-place manipulation.

  • The Keys iterator now implements Index<usize> for quick access to the entry's key, compared to indexing the map to get the value.

  • The new IndexMap::splice and IndexSet::splice methods will drain the given range as an iterator, and then replace that range with entries from an input iterator.

  • The new trait RawEntryApiV1 offers opt-in access to a raw entry API for IndexMap, corresponding to the unstable API on HashSet as of Rust 1.75.

  • Many IndexMap and IndexSet methods have relaxed their type constraints, e.g. removing K: Hash on methods that don't actually need to hash.

  • Removal methods remove, remove_entry, and take are now deprecated in favor of their shift_ or swap_ prefixed variants, which are more explicit about their effect on the index and order of remaining items. The deprecated methods will remain to guide drop-in replacements from HashMap and HashSet toward the prefixed methods.

Commits

• 7264ce4 Merge pull request #304 from cuviper/raw-into_key
• 244bd81 Fix RawOccupiedEntryMut::into_key
• 7107c49 Merge pull request #303 from cuviper/test-updates
• 34a7af7 Allow clippy::style
• 382a45c Upgrade dev-dep itertools to 0.12
• 904689f ci: upgrade to actions/checkout@v4
• 405fa10 Merge pull request #302 from cuviper/release-2.2.0
• d84bf5e Release 2.2.0
• 9edb1a4 Merge pull request #300 from cuviper/raw_entry_v1
• a1495fd Merge pull request #301 from cuviper/unstringify
• Additional commits viewable in compare view

Updates itertools from 0.12.0 to 0.12.1

Changelog

Sourced from itertools's changelog.

0.12.1

Added

• Documented iteration order guarantee for Itertools::[tuple_]combinations (#822)
• Documented possible panic in iterate (#842)
• Implemented Clone and Debug for Diff (#845)
• Implemented Debug for WithPosition (#859)
• Implemented Eq for MinMaxResult (#838)
• Implemented From<EitherOrBoth<A, B>> for Option<Either<A, B>> (#843)
• Implemented PeekingNext for RepeatN (#855)

Changed

• Made CoalesceBy lazy (#801)
• Optimized Filter[Map]Ok::next, Itertools::partition, Unique[By]::next[_back] (#818)
• Optimized Itertools::find_position (#837)
• Optimized Positions::next[_back] (#816)
• Optimized ZipLongest::fold (#854)
• Relaxed Debug bounds for GroupingMapBy (#860)
• Specialized ExactlyOneError::fold (#826)
• Specialized Interleave[Shortest]::fold (#849)
• Specialized MultiPeek::fold (#820)
• Specialized PadUsing::[r]fold (#825)
• Specialized PeekNth::fold (#824)
• Specialized Positions::[r]fold (#813)
• Specialized PutBackN::fold (#823)
• Specialized RepeatN::[r]fold (#821)
• Specialized TakeWhileInclusive::fold (#851)
• Specialized ZipLongest::rfold (#848)

Notable Internal Changes

• Added test coverage in CI (#847, #856)
• Added semver check in CI (#784)
• Enforced clippy in CI (#740)
• Enforced rustdoc in CI (#840)
• Improved specialization tests (#807)
• More specialization benchmarks (#806)

Commits

• 98d3978 Prepare v0.12.1 release
• dffac1f Bump obi1kenobi/cargo-semver-checks-action from 2.2 to 2.3
• 00998a4 CoalesceBy: missing field in Debug
• a0411d6 CombinationsWithReplacement: use a boxed slice internally
• 8dd75f1 Permutations: use boxed slices internally
• b785403 ExactlyOneError: implement Debug differently
• 7a1c22b FlattenOk: Debug with macro
• 94452e3 GroupingMapBy: fix Debug implementation
• 2e325a0 TakeWhileInclusive: missing field in Debug
• a48c5b4 WithPosition: implement Debug
• Additional commits viewable 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 strum from 0.25.0 to 0.26.1

Changelog

Sourced from strum's changelog.

0.26.1

• #325: use core instead of std in VariantArray.

0.26.0

Breaking Changes

• The EnumVariantNames macro has been renamed VariantNames. The deprecation warning should steer you in the right direction for fixing the warning.
• The Iterator struct generated by EnumIter now has new bounds on it. This shouldn't break code unless you manually added the implementation in your code.
• Display now supports format strings using named fields in the enum variant. This should be a no-op for most code. However, if you were outputting a string like "Hello {field}", this will now be interpretted as a format string.
• EnumDiscriminant now inherits the repr and discriminant values from your main enum. This makes the discriminant type closer to a mirror of the original and that's always the goal.

New features

• The VariantArray macro has been added. This macro adds an associated constant VARIANTS to your enum. The constant is a &'static [Self] slice so that you can access all the variants of your enum. This only works on enums that only have unit variants.

  use strum::VariantArray;
  #[derive(Debug, VariantArray)]
  enum Color {
  Red,
  Blue,
  Green,
  }
  fn main() {
  println!("{:?}", Color::VARIANTS); // prints: ["Red", "Blue", "Green"]
  }

• The EnumTable macro has been experimentally added. This macro adds a new type that stores an item for each variant of the enum. This is useful for storing a value for each variant of an enum. This is an experimental feature because I'm not convinced the current api surface area is correct.

  use strum::EnumTable;
  #[derive(Copy, Clone, Debug, EnumTable)]
  enum Color {
  Red,
  Blue,
  Green,

... (truncated)

Commits

• See full diff in compare view

Updates strum_macros from 0.25.3 to 0.26.1

Changelog

Sourced from strum_macros's changelog.

0.26.1

• #325: use core instead of std in VariantArray.

0.26.0

Breaking Changes

• The EnumVariantNames macro has been renamed VariantNames. The deprecation warning should steer you in the right direction for fixing the warning.
• The Iterator struct generated by EnumIter now has new bounds on it. This shouldn't break code unless you manually added the implementation in your code.
• Display now supports format strings using named fields in the enum variant. This should be a no-op for most code. However, if you were outputting a string like "Hello {field}", this will now be interpretted as a format string.
• EnumDiscriminant now inherits the repr and discriminant values from your main enum. This makes the discriminant type closer to a mirror of the original and that's always the goal.

New features

• The VariantArray macro has been added. This macro adds an associated constant VARIANTS to your enum. The constant is a &'static [Self] slice so that you can access all the variants of your enum. This only works on enums that only have unit variants.

  use strum::VariantArray;
  #[derive(Debug, VariantArray)]
  enum Color {
  Red,
  Blue,
  Green,
  }
  fn main() {
  println!("{:?}", Color::VARIANTS); // prints: ["Red", "Blue", "Green"]
  }

• The EnumTable macro has been experimentally added. This macro adds a new type that stores an item for each variant of the enum. This is useful for storing a value for each variant of an enum. This is an experimental feature because I'm not convinced the current api surface area is correct.

  use strum::EnumTable;
  #[derive(Copy, Clone, Debug, EnumTable)]
  enum Color {
  Red,
  Blue,
  Green,

... (truncated)

Commits

• See full diff 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