Bump the rust-dependencies group with 6 updates

[dependabot]

Bumps the rust-dependencies group with 6 updates:

Package	From	To
lalrpop-util	0.20.2	0.22.0
regex	1.10.5	1.11.1
thiserror	1.0.63	2.0.3
serde_json	1.0.120	1.0.133
serde	1.0.204	1.0.215
lalrpop	0.20.2	0.22.0

Updates lalrpop-util from 0.20.2 to 0.22.0

Changelog

Sourced from lalrpop-util's changelog.

0.22.0 (2024-09-26)

Breaking changes

• The lexer feature no longer implies the std feature. Now lexer is usable in no_std environments. In no_std, ParseError only implements the Error trait in rust 1.81 or later (since core::error was stablized in 1.81).

Features

• Overhaul cfg attributes. You can now include or omit grammar rules and alternatives based on cargo features with not(), any() and all() support

Bugfixes

• Improvements to error message reporting to improve clarity and suppress extra noise
• lalrpop_mod!() now handles imports correctly
• Reenable some warnings on user code for custom lexers

0.21.0 (2024-05-30)

Since the last release, a fair number of the commits have been focused on cleaning up and improving LALRPOP's documentation. Shout out to Yudai Takada, George White, and Dinu Blanovschi.

Features

• LALRPOP now throws an error in more cases where it would previously just write out an error message and exit.
• lalrpop::process_src is now the recommended function to use in build.rs files. Previously the documentation incorrectly suggested that lalrpop::process_root looked in ./src instead of .

Bugfixes

• A long-standing bug where LALRPOP would throw a "no entry found for key" exception when trying to handle certain grammars has been resolved.
• LALRPOP will stop expanding macros infinitely during build time via a new macro_expansion_limit.

Compatibility note

Adding a limit to the number of times that LALRPOP will attempt to expand a macro is technically a breaking change. However, the default limit of 200 should be more than enough for the grammars we are currently aware of (which almost always need a limit of less than 5). This limit is customizable via Configuration::set_macro_expansion_limit.

If you have a grammar that uses a significant amount of macro expansion steps, we would be very interested in a PR that adds it to the test suite.

Commits

• 49b3c2c Release version 0.22.0 (#953)
• bb98e93 When encountering naive errors on reduce/reduce conflicts, drop all but (#938)
• 1b3587d Cfg attibutes on Alternatives (#959)
• 55d1c3b Add a new error message for ambiguous reductions to the same nonterminal (#927)
• 2fb8a29 Lock rustversion (#964)
• d6229c8 Update to ascii-canvas 4.0 and term 1.0 (#963)
• fb9a945 Support Error with std feature disabled (#957)
• 2cd9a59 Turn a few warnings back on when we match token values (#961)
• 0c41809 Kind of unify version.sh regex search (#958)
• 2498289 Mention the clog-cli prereq in the CONTRIBUTING release process (#954)
• Additional commits viewable in compare view

Updates regex from 1.10.5 to 1.11.1

Changelog

Sourced from regex's changelog.

1.11.1 (2024-10-24)

This is a new patch release of regex that fixes compilation on nightly Rust when the unstable pattern crate feature is enabled. Users on nightly Rust without this feature enabled are unaffected.

Bug fixes:

• [BUG #1231](rust-lang/regex#1231): Fix the Pattern trait implementation as a result of nightly API breakage.

1.11.0 (2024-09-29)

This is a new minor release of regex that brings in an update to the Unicode Character Database. Specifically, this updates the Unicode data used by regex internally to the version 16 release.

New features:

• [FEATURE #1228](rust-lang/regex#1228): Add new regex::SetMatches::matched_all method.
• [FEATURE #1229](rust-lang/regex#1229): Update to Unicode Character Database (UCD) version 16.

1.10.6 (2024-08-02)

This is a new patch release with a fix for the unstable crate feature that enables std::str::Pattern trait integration.

Bug fixes:

• [BUG #1219](rust-lang/regex#1219): Fix the Pattern trait implementation as a result of nightly API breakage.

Commits

• 9870c06 1.11.1
• 80df54e changelog: 1.11.1
• 991ba88 unstable: fix Pattern trait implementation
• bcbe403 1.11.0
• 9e17e56 deps: bump regex-automata
• 58e16f5 regex-automata-0.4.8
• 4bb1e3d deps: bump regex-syntax
• cba0fbc regex-syntax-0.8.5
• 1533257 changelog: 1.11.0
• 9239e7e data: update to UCD 16
• Additional commits viewable in compare view

Updates thiserror from 1.0.63 to 2.0.3

Release notes

Sourced from thiserror's releases.

2.0.3

• Support the same Path field being repeated in both Debug and Display representation in error message (#383)
• Improve error message when a format trait used in error message is not implemented by some field (#384)

2.0.2

• Fix hang on invalid input inside #[error(...)] attribute (#382)

2.0.1

• Support errors that contain a dynamically sized final field (#375)
• Improve inference of trait bounds for fields that are interpolated multiple times in an error message (#377)

2.0.0

Breaking changes

• Referencing keyword-named fields by a raw identifier like {r#type} inside a format string is no longer accepted; simply use the unraw name like {type} (#347)

  This aligns thiserror with the standard library's formatting macros, which gained support for implicit argument capture later than the release of this feature in thiserror 1.x.

  #[derive(Error, Debug)]
  #[error("... {type} ...")]  // Before: {r#type}
  pub struct Error {
      pub r#type: Type,
  }

• Trait bounds are no longer inferred on fields whose value is shadowed by an explicit named argument in a format message (#345)

  // Before: impl<T: Octal> Display for Error<T>
  // After: impl<T> Display for Error<T>
  #[derive(Error, Debug)]
  #[error("{thing:o}", thing = "...")]
  pub struct Error<T> {
      thing: T,
  }

• Tuple structs and tuple variants can no longer use numerical {0} {1} access at the same time as supplying extra positional arguments for a format message, as this makes it ambiguous whether the number refers to a tuple field vs a different positional arg (#354)

  #[derive(Error, Debug)]
  #[error("ambiguous: {0} {}", $N)]
  //                  ^^^ Not allowed, use #[error("... {0} {n}", n = $N)]
  pub struct TupleError(i32);

• Code containing invocations of thiserror's derive(Error) must now have a direct dependency on the thiserror crate regardless of the error data structure's contents (#368, #369, #370, #372)

Features

... (truncated)

Commits

• 15fd26e Release 2.0.3
• 7046023 Simplify how has_bonus_display is accumulated
• 9cc1d0b Merge pull request #384 from dtolnay/nowrap
• 1d040f3 Use Var wrapper only for Pointer formatting
• 6a6132d Extend no-display ui test to cover another fmt trait
• a061beb Merge pull request #383 from dtolnay/both
• 6388293 Support Display and Debug of same path in error message
• dc0359e Defer binding_value construction
• 520343e Add test of Debug and Display of paths
• 49be39d Release 2.0.2
• Additional commits viewable in compare view

Updates serde_json from 1.0.120 to 1.0.133

Release notes

Sourced from serde_json's releases.

v1.0.133

• Implement From<[T; N]> for serde_json::Value (#1215)

v1.0.132

• Improve binary size and compile time for JSON array and JSON object deserialization by about 50% (#1205)
• Improve performance of JSON array and JSON object deserialization by about 8% (#1206)

v1.0.131

• Implement Deserializer and IntoDeserializer for Map<String, Value> and &Map<String, Value> (#1135, thanks @​swlynch99)

v1.0.130

• Support converting and deserializing Number from i128 and u128 (#1141, thanks @​druide)

v1.0.129

• Add serde_json::Map::sort_keys and serde_json::Value::sort_all_objects (#1199)

v1.0.128

• Support serializing maps containing 128-bit integer keys to serde_json::Value (#1188, thanks @​Mrreadiness)

v1.0.127

• Add more removal methods to OccupiedEntry (#1179, thanks @​GREsau)

v1.0.126

• Improve string parsing on targets that use 32-bit pointers but also have fast 64-bit integer arithmetic, such as aarch64-unknown-linux-gnu_ilp32 and x86_64-unknown-linux-gnux32 (#1182, thanks @​CryZe)

v1.0.125

• Speed up \uXXXX parsing and improve handling of unpaired surrogates when deserializing to bytes (#1172, #1175, thanks @​purplesyringa)

v1.0.124

• Fix a bug in processing string escapes in big-endian architectures (#1173, thanks @​purplesyringa)

v1.0.123

• Optimize string parsing by applying SIMD-within-a-register: 30.3% improvement on twitter.json from 613 MB/s to 799 MB/s (#1161, thanks @​purplesyringa)

v1.0.122

• Support using json! in no-std crates (#1166)

v1.0.121

• Optimize position search in error path (#1160, thanks @​purplesyringa)

Commits

• 0903de4 Release 1.0.133
• 2b65ca0 Merge pull request #1215 from dtolnay/fromarray
• 4e5f985 Implement From<[T; N]> for Value
• 2ccb5b6 Disable question_mark clippy lint in lexical test
• a11f5f2 Resolve unnecessary_map_or clippy lints
• 07f280a Wrap PR 1213 to 80 columns
• 75ed447 Merge pull request #1213 from djmitche/safety-comment
• 73011c0 Add a safety comment to unsafe block
• be2198a Prevent upload-artifact step from causing CI failure
• 7cce517 Raise minimum version for preserve_order feature to Rust 1.65
• Additional commits viewable in compare view

Updates serde from 1.0.204 to 1.0.215

Release notes

Sourced from serde's releases.

v1.0.215

• Produce warning when multiple fields or variants have the same deserialization name (#2855, #2856, #2857)

v1.0.214

• Implement IntoDeserializer for all Deserializers in serde::de::value module (#2568, thanks @​Mingun)

v1.0.213

• Fix support for macro-generated with attributes inside a newtype struct (#2847)

v1.0.212

• Fix hygiene of macro-generated local variable accesses in serde(with) wrappers (#2845)

v1.0.211

• Improve error reporting about mismatched signature in with and default attributes (#2558, thanks @​Mingun)
• Show variant aliases in error message when variant deserialization fails (#2566, thanks @​Mingun)
• Improve binary size of untagged enum and internally tagged enum deserialization by about 12% (#2821)

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)

v1.0.209

• Fix deserialization of empty structs and empty tuples inside of untagged enums (#2805, thanks @​Mingun)

v1.0.208

• Support serializing and deserializing unit structs in a flatten field (#2802, thanks @​jonhoo)

v1.0.207

• Improve interactions between flatten attribute and skip_serializing/skip_deserializing (#2795, thanks @​Mingun)

v1.0.206

• Improve support for flatten attribute inside of enums (#2567, thanks @​Mingun)

v1.0.205

• Use serialize_entry instead of serialize_key + serialize_value when serialize flattened newtype enum variants (#2785, thanks @​Mingun)
• Avoid triggering a collection_is_never_read lint in the deserialization of enums containing flattened fields (#2791)

Commits

• 8939af4 Release 1.0.215
• fa5d58c Use ui test syntax that does not interfere with rustfmt
• 1a3cf4b Update PR 2562 ui tests
• 7d96352 Merge pull request #2857 from dtolnay/collide
• 111ecc5 Update ui tests for warning on colliding aliases
• edd6fe9 Revert "Add checks for conflicts for aliases"
• a20e924 Revert "pacify clippy"
• b1353a9 Merge pull request #2856 from dtolnay/dename
• c59e876 Produce a separate warning for every colliding name
• 7f1e697 Merge pull request #2855 from dtolnay/namespan
• Additional commits viewable in compare view

Updates lalrpop from 0.20.2 to 0.22.0

Changelog

Sourced from lalrpop's changelog.

0.22.0 (2024-09-26)

Breaking changes

• The lexer feature no longer implies the std feature. Now lexer is usable in no_std environments. In no_std, ParseError only implements the Error trait in rust 1.81 or later (since core::error was stablized in 1.81).

Features

• Overhaul cfg attributes. You can now include or omit grammar rules and alternatives based on cargo features with not(), any() and all() support

Bugfixes

• Improvements to error message reporting to improve clarity and suppress extra noise
• lalrpop_mod!() now handles imports correctly
• Reenable some warnings on user code for custom lexers

0.21.0 (2024-05-30)

Since the last release, a fair number of the commits have been focused on cleaning up and improving LALRPOP's documentation. Shout out to Yudai Takada, George White, and Dinu Blanovschi.

Features

• LALRPOP now throws an error in more cases where it would previously just write out an error message and exit.
• lalrpop::process_src is now the recommended function to use in build.rs files. Previously the documentation incorrectly suggested that lalrpop::process_root looked in ./src instead of .

Bugfixes

• A long-standing bug where LALRPOP would throw a "no entry found for key" exception when trying to handle certain grammars has been resolved.
• LALRPOP will stop expanding macros infinitely during build time via a new macro_expansion_limit.

Compatibility note

Adding a limit to the number of times that LALRPOP will attempt to expand a macro is technically a breaking change. However, the default limit of 200 should be more than enough for the grammars we are currently aware of (which almost always need a limit of less than 5). This limit is customizable via Configuration::set_macro_expansion_limit.

If you have a grammar that uses a significant amount of macro expansion steps, we would be very interested in a PR that adds it to the test suite.

Commits

• 49b3c2c Release version 0.22.0 (#953)
• bb98e93 When encountering naive errors on reduce/reduce conflicts, drop all but (#938)
• 1b3587d Cfg attibutes on Alternatives (#959)
• 55d1c3b Add a new error message for ambiguous reductions to the same nonterminal (#927)
• 2fb8a29 Lock rustversion (#964)
• d6229c8 Update to ascii-canvas 4.0 and term 1.0 (#963)
• fb9a945 Support Error with std feature disabled (#957)
• 2cd9a59 Turn a few warnings back on when we match token values (#961)
• 0c41809 Kind of unify version.sh regex search (#958)
• 2498289 Mention the clog-cli prereq in the CONTRIBUTING release process (#954)
• 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