Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update all dependencies #5

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update all dependencies #5

wants to merge 1 commit into from

Conversation

kjuulh
Copy link
Owner

@kjuulh kjuulh commented Apr 19, 2024

This PR contains the following updates:

Package Type Update Change
anyhow workspace.dependencies patch 1.0.75 -> 1.0.82
async-trait workspace.dependencies patch 0.1.73 -> 0.1.80
base64 dependencies minor 0.21.4 -> 0.22.0
bytes workspace.dependencies minor 1.5 -> 1.6
capnp dependencies minor 0.18.1 -> 0.19.3
capnpc build-dependencies minor 0.18.0 -> 0.19.0
chrono workspace.dependencies patch 0.4.31 -> 0.4.38
clap workspace.dependencies minor 4.4.5 -> 4.5.4
genco workspace.dependencies patch 0.17.6 -> 0.17.8
inquire workspace.dependencies minor 0.6.2 -> 0.7.4
nats workspace.dependencies patch 0.24.0 -> 0.24.1
regex workspace.dependencies minor 1.9.5 -> 1.10.4
serde (source) dependencies patch 1.0.188 -> 1.0.198
serde (source) workspace.dependencies patch 1.0.188 -> 1.0.198
serde_json dependencies patch 1.0.107 -> 1.0.116
serde_json workspace.dependencies patch 1.0.107 -> 1.0.116
sqlx workspace.dependencies patch 0.7.2 -> 0.7.4
tempfile (source) workspace.dependencies minor 3.8.0 -> 3.10.1
thiserror workspace.dependencies patch 1.0.48 -> 1.0.58
tokio-stream (source) workspace.dependencies patch 0.1.14 -> 0.1.15
toml_edit workspace.dependencies minor 0.20.0 -> 0.22.11
tracing-subscriber (source) workspace.dependencies patch 0.3.17 -> 0.3.18
uuid workspace.dependencies minor 1.4.1 -> 1.8.0
walkdir workspace.dependencies minor 2.4.0 -> 2.5.0

Release Notes

dtolnay/anyhow

v1.0.82

Compare Source

  • Documentation improvements

v1.0.81

Compare Source

  • Make backtrace support available when using -Dwarnings (#​354)

v1.0.80

Compare Source

  • Fix unused_imports warnings when compiled by rustc 1.78

v1.0.79

Compare Source

  • Work around improperly cached build script result by sccache (#​340)

v1.0.78

Compare Source

  • Reduce spurious rebuilds under RustRover IDE when using a nightly toolchain (#​337)

v1.0.77

Compare Source

v1.0.76

Compare Source

  • Opt in to unsafe_op_in_unsafe_fn lint (#​329)
dtolnay/async-trait

v0.1.80

Compare Source

v0.1.79

Compare Source

  • Clean up some dead code

v0.1.78

Compare Source

  • Prevent unused_qualifications lint being triggered in generated code in nightly-2024-03-05 and up (#​260)

v0.1.77

Compare Source

  • Update proc-macro2 to fix caching issue when using a rustc-wrapper such as sccache

v0.1.76

Compare Source

  • Documentation improvements

v0.1.75

Compare Source

  • Documentation improvements

v0.1.74

Compare Source

  • Documentation improvements
marshallpierce/rust-base64

v0.22.0

Compare Source

  • DecodeSliceError::OutputSliceTooSmall is now conservative rather than precise. That is, the error will only occur if the decoded output cannot fit, meaning that Engine::decode_slice can now be used with exactly-sized output slices. As part of this, Engine::internal_decode now returns DecodeSliceError instead of DecodeError, but that is not expected to affect any external callers.
  • DecodeError::InvalidLength now refers specifically to the number of valid symbols being invalid (i.e. len % 4 == 1), rather than just the number of input bytes. This avoids confusing scenarios when based on interpretation you could make a case for either InvalidLength or InvalidByte being appropriate.
  • Decoding is somewhat faster (5-10%)

v0.21.7

Compare Source

  • Support getting an alphabet's contents as a str via Alphabet::as_str()

v0.21.6

Compare Source

  • Improved introductory documentation and example

v0.21.5

Compare Source

  • Add Debug and Clone impls for the general purpose Engine
tokio-rs/bytes

v1.6.0

Compare Source

Added
Documented
Internal changes
  • Move comment to correct constant (#​629)
  • Various cleanup (#​635)
  • Simplify UninitSlice::as_uninit_slice_mut() logic (#​644)
  • Use self. instead of Self:: (#​642)
  • BytesMut: Assert alignment of Shared (#​652)
  • Remove unnecessary namespace qualifier (#​660)
  • Remove an unnecessary else branch (#​662)
  • Remove unreachable else branch (#​661)
  • make parameter mut in From<Vec> (#​667)
  • Restore commented tests (#​665)
  • Use sub instead of offset (#​668)
  • Calculate original capacity only if necessary (#​666)
  • set_vec_pos does not need a second parameter (#​672)
  • get_vec_pos: use &self instead of &mut self (#​670)
  • Refactor split_at/split_to (#​663)
  • Use Iterator from the prelude (#​673)
  • copy_to_bytes: Add panic section to docs (#​676)
  • Remove redundant reserve call (#​674)
  • Use ManuallyDrop instead of mem::forget (#​675)
capnproto/capnproto-rust

v0.19.3

Compare Source

v0.19.2

Compare Source

v0.19.1

Compare Source

v0.19.0

Compare Source

v0.18.13

Compare Source

v0.18.12

Compare Source

v0.18.11

Compare Source

v0.18.10

Compare Source

v0.18.9

Compare Source

v0.18.8

Compare Source

v0.18.7

Compare Source

v0.18.6

Compare Source

v0.18.5

Compare Source

v0.18.4

Compare Source

v0.18.3

Compare Source

v0.18.2

Compare Source

chronotope/chrono

v0.4.38

Compare Source

This release bring a ca. 20% improvement to the performance of the formatting code, and a convenient days_since method for the Weekday type.

Chrono 0.4.38 also removes the long deprecated rustc-serialize feature. Support for rustc-serialize will be soft-destabilized in the next Rust edition. Removing the feature will not break existing users of the feature; Cargo will just not update dependents that rely on it to newer versions of chrono.

In chrono 0.4.36 we made an accidental breaking change by switching to derive(Copy) for DateTime instead of a manual implementation. It is reverted in this release.

Removals
Additions
Fixes
  • Return error when rounding with a zero duration (#​1474, thanks @​Dav1dde)
  • Manually implement Copy for DateTime if offset is Copy (#​1573)
Internal
  • Inline test_encodable_json and test_decodable_json functions (#​1550)
  • CI: Reduce combinations in cargo hack check (#​1553)
  • Refactor formatting code (#​1335)
  • Optimize number formatting (#​1558)
  • Only package files needed for building and testing (#​1554)

Thanks to all contributors on behalf of the chrono team, @​djc and @​pitdicker!

v0.4.37

Compare Source

Version 0.4.36 introduced an unexpected breaking change and was yanked. In it LocalResult was renamed to MappedLocalTime to avoid the impression that it is a Result type were some of the results are errors. For backwards compatibility a type alias with the old name was added.

As it turns out there is one case where a type alias behaves differently from the regular enum: you can't import enum variants from a type alias with use chrono::LocalResult::*. With 0.4.37 we make the new name MappedLocalTime the alias, but keep using it in function signatures and the documentation as much as possible.

See also the release notes of chrono 0.4.36 from yesterday for the yanked release.

v0.4.36

Compare Source

This release un-deprecates the methods on TimeDelta that were deprecated with the 0.4.35 release because of the churn they are causing for the ecosystem.

New is the DateTime::with_time() method. As an example of when it is useful:

use chrono::{Local, NaiveTime};
// Today at 12:00:00
let today_noon = Local::now().with_time(NaiveTime::from_hms_opt(12, 0, 0).unwrap());

Additions

Deprecations

  • Revert TimeDelta deprecations (#​1543)
  • Deprecate TimeStamp::timestamp_subsec_nanos, which was missed in the 0.4.35 release (#​1486)

Documentation

  • Correct version number of deprecation notices (#​1486)
  • Fix some typos (#​1505)
  • Slightly improve serde documentation (#​1519)
  • Main documentation: simplify links and reflow text (#​1535)

Internal

  • CI: Lint benchmarks (#​1489)
  • Remove unnessary Copy and Send impls (#​1492, thanks @​erickt)
  • Backport streamlined NaiveDate unit tests (#​1500, thanks @​Zomtir)
  • Rename LocalResult to TzResolution, add alias (#​1501)
  • Update windows-bindgen to 0.55 (#​1504)
  • Avoid duplicate imports, which generate warnings on nightly (#​1507)
  • Add extra debug assertions to NaiveDate::from_yof (#​1518)
  • Some small simplifications to DateTime::date_naive and NaiveDate::diff_months (#​1530)
  • Remove unwrap in Unix Local type (#​1533)
  • Use different method to ignore feature-dependent doctests (#​1534)

Thanks to all contributors on behalf of the chrono team, @​djc and @​pitdicker!

v0.4.35

Compare Source

Most of our efforts have shifted to improving the API for a 0.5 release, for which cleanups and refactorings are landing on the 0.4.x branch.

The most significant changes in this release are two sets of deprecations.

  • We deprecated all timestamp-related methods on NaiveDateTime. The reason is that a timestamp is defined to be in UTC. The NaiveDateTime type doesn't know the offset from UTC, so it was technically wrong to have these methods. The alternative is to use the similar methods on the DateTime<Utc> type, or from the TimeZone trait.

    Converting from NaiveDateTime to DateTime<Utc> is simple with .and_utc(), and in the other direction with .naive_utc().

  • The panicking constructors of TimeDelta (the new name of the Duration type) are deprecated. This was the last part of chrono that defaulted to panicking on error, dating from before rust 1.0.

  • A nice change is that NaiveDate now includes a niche. So now Option<NaiveDate>, Option<NaiveDateTime> and Option<DateTime<Tz>> are the same size as their base types.

  • format::Numeric and format::Fixed are marked as non_exhaustive. This will allow us to improve our formatting and parsing support, and we have reason to believe this breaking change will have little to no impact on users.

Additions

  • Add DateTime::{from_timestamp_micros, from_timestamp_nanos} (#​1234)
  • Add getters to Parsed (#​1465)

Deprecations

  • Deprecate timestamp methods on NaiveDateTime (#​1473)
  • Deprecate panicking constructors of TimeDelta (#​1450)

Changes/fixes

  • Use NonZeroI32 inside NaiveDate (#​1207)
  • Mark format::Numeric and format::Fixed as non_exhaustive (#​1430)
  • Parsed fixes to error values (#​1439)
  • Use overflowing_naive_local in DateTime::checked_add* (#​1333)
  • Do complete range checks in Parsed::set_* (#​1465)

Documentation

Internal

Thanks to all contributors on behalf of the chrono team, @​djc and @​pitdicker!

v0.4.34

Compare Source

Notable changes

  • In chrono 0.4.34 we finished the work to make all methods const where doing so is supported by rust 1.61.
  • We renamed the Duration type to TimeDelta. This removes the confusion between chrono's type and the later Duration type in the standard library. It will remain available under the old name as a type alias for compatibility.
  • The Windows implementation of Local is rewritten. The new version avoids panics when the date is outside of the range supported by windows (the years 1601 to 30828), and gives more accurate results during DST transitions.
  • The Display format of TimeDelta is modified to conform better to ISO 8601. Previously it converted all values greater than 24 hours to a value with days. This is not correct, as doing so changes the duration from an 'accurate' to a 'nominal' representation to use ISO 8601 terms.

Fixes

Additions

Changes

  • Rename Duration to TimeDelta, add type alias (#​1406)
  • Make TimeDelta methods const (#​1337)
  • Make remaining methods of NaiveDate, NaiveWeek, NaiveTime and NaiveDateTime const where possible (#​1337)
  • Make methods on DateTime const where possible (#​1400)
  • Make Display format of TimeDelta conform better to ISO 8601 (#​1328)

Documentation

Internal

  • Switch branch names: 0.4.x releases are the main branch, work on 0.5 happens in the 0.5.x branch (#​1390, #​1402).
  • Don't use deprecated method in impl Arbitrary for DateTime and set up CI test (#​1336)
  • Remove workaround for Rust < 1.61 (#​1393)
  • Bump codecov/codecov-action from 3 to 4 (#​1404)
  • Remove partial support for handling -0000 offset (#​1411)
  • Move TOO_LONG error out of parse_internal (#​1419)

Thanks to all contributors on behalf of the chrono team, @​djc and @​pitdicker!

v0.4.33

Compare Source

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

What's Changed

v0.4.32

Compare Source

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

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

Rkyv support

Changes to unstable features

  • Don't let unstable-locales imply the alloc feature (#​1307)
  • Remove format::{format_localized, format_item_localized} (#​1311)
  • Inline write_rfc2822_inner, don't localize (#​1322)

Internal

  • Add benchmark for DateTime::with_* (#​1309)
  • Fix *_DAYS_FROM_YEAR_0 calculation (#​1312)
  • Add NaiveTime::overflowing_(add|sub)_offset (#​1310)
  • Rewrite DateTime::overflowing_(add|sub)_offset (#​1069)
  • Tests calling date command set env LC_ALL (#​1315, thanks @​jtmoon79)
  • Update deny.toml (#​1320)
  • Bump actions/setup-node from 3 to 4 (#​1346)
  • test.yml remove errant with: node-version (#​1352, thanks @​jtmoon79)
  • CI Linting: Fix missing sources checkout in toml job (#​1371, thanks @​gibbz00)
  • Silence clippy lint for test code with Rust 1.74.0 (#​1362)

Thanks to all contributors on behalf of the chrono team, @​djc and @​pitdicker!

clap-rs/clap

v4.5.4

Compare Source

Fixes
  • (derive) Allow non-literal #[arg(id)] attributes again

v4.5.3

Compare Source

Internal
  • (derive) Update heck

v4.5.2

Compare Source

Fixes
  • (macros) Silence a warning

v4.5.1

Compare Source

Fixes
  • (error) Include suggestion to add -- even if there is a "did you mean" so long as last or trailing_var_arg is used

v4.5.0

Compare Source

Compatibility
  • Update MSRV to 1.74

v4.4.18

Compare Source

Fixes
  • (error) When lacking usage feature, ensure the list of required arguments is unique

v4.4.17

Compare Source

Fixes
  • Fix panic! when mixing args_conflicts_with_subcommands with ArgGroup (which is implicit with derive) introduced in 4.4.15

v4.4.16

Compare Source

Fixes
  • Ensure invalid escape sequences in user-defined strings are correctly stripped when terminal doesn't support color

v4.4.15

Compare Source

Fixes
  • Improve error for args_conflicts_with_subcommands
  • Ensure we error for args_conflicts_with_subcommands when using subcommand short and long flags

v4.4.14

Compare Source

Documentation
  • Fix find cookbook entry to allow repeats of flags/options
Features
  • Allow num_args(0) on options which allows making them emulate being a flag for position-tracking flags

v4.4.13

Compare Source

Documentation
  • Fix link to structopt migration guide

v4.4.12

Compare Source

Performance
  • Only ask TypedValueParser for possible values if needed

v4.4.11

Compare Source

Features
  • Add Command::mut_group

v4.4.10

Compare Source

Documentation
  • Link out to changelog
  • Cross link derive's attribute reference to derive tutorial

v4.4.9

Compare Source

Fixes
  • (help) Show correct Command::about under flattened headings
  • (help) Respect hide when flattening subcommands

v4.4.8

Compare Source

Features
  • Add Command::flatten_help to allow git stash -h like help for subcommands

v4.4.7

Compare Source

Performance
  • Reduced code size

v4.4.6

Compare Source

Internal
  • Upgrade anstream
udoprog/genco

v0.17.8

Compare Source

What's Changed

Full Changelog: udoprog/genco@0.17.7...0.17.8

v0.17.7

Compare Source

What's Changed

New Contributors

Full Changelog: udoprog/genco@0.17.6...0.17.7

mikaelmello/inquire

v0.7.4

Compare Source

  • Fix unexpected behaviors of keep_filter option in MultiSelect prompts:
    • Filter input is now correcly getting reset only when keep_filter == false.
    • When the filter input is reset, the list of options is now correctly reset as well. Thanks @​Swivelgames for reporting #​238.

v0.7.3

Compare Source

  • Fix cursor occasionally blinking in unexpected places.

v0.7.2

Compare Source

  • Pressing Ctrl+D now cancels the prompt. Thanks @​mikecvet for the PR!
  • Add support for h and l bindings when vim_mode is enabled on MultiSelect prompts, clearing or selecting all options respectively. Thanks @​afh for the PR!
  • Fix render issue #​233 where cursor positioning at the end of a prompt was incorrect. Thanks @​msrd0 and @​Sydonian for reporting!

v0.7.1

Compare Source

  • Fix render issue #​228 when using console crate as the terminal backend. Thanks @​maospr for reporting.

v0.7.0

Compare Source

Breaking Changes
  • The Select and Multiselect Filter now scores input and is now expected to return an Option<i64>, making it possible to order/rank the list of options. #​176
    None: Will not be displayed in the list of options.
    Some(score): score determines the order of options, higher score, higher on the list of options.
  • Improved user experience on Password prompts. When there is a validation error, the input is cleared if the password is rendered using the Hidden display mode, matching the user expectation of having to write the password from scratch again. Thanks to @​CM-IV for the questions on #​149!
  • Allow lifetime customization of RenderConfig. #​101. Thanks to @​arturfast for the suggestion #​95.
  • Implement fuzzy search as default on Select and MultiSelect prompts. #​176
  • Revamped keybindings for DateSelect.
Features
  • Add one-liner helpers for quick scripts. #​144.
  • Add new option on MultiSelect prompts to set all options to be selected by default. Thanks to @​conikeec for the suggestion (#​151)!
  • Add new option on Select/MultiSelect prompts allowing to reset selection to the first item on filter-input changes. #​176
  • Emacs-like keybindings added where applicable:
    • Ctrl-p/Ctrl-n for up/down
    • Ctrl-b/Ctrl-f for left/right
    • Ctrl-j/Ctrl-g for enter/cancel
  • Vim keybindings are always supported in DateSelect prompts.
  • Added 'with_starting_filter_input' to both Select and MultiSelect, which allows for setting an initial value to the filter section of the prompt.
  • Added starting_input for CustomType. #​194
  • Added 'without_filtering' to both Select and MultiSelect, useful when you want to simplify the UX if the filter does not add any value, such as when the list is already short.
  • Added 'with_answered_prompt_prefix' to RenderConfig to allow customization of answered prompt prefix.
  • Improved rendering, with optimizations on incremental rendering and terminal resizing.
Fixes
  • Fixed typos in the code's comments.
  • Fixed issue where inquire, using termion, would crash when receiving piped inputs.
Dependency changes (some breaking)
  • Upgraded underlying termion crate from v1.5 to v2.0.
  • Upgraded underlying bitflags from v1 to v2, which affects the Attributes and KeyModifiers crates. If you use any of bitflag's methods directly, you might be affected, refer to the bitflags changelog for more information.
  • Removed thiserror dependency in favor of implementing InquireError by hand. #​146
  • Raised MSRV to 1.66 due to requirements in downstream dependencies.
  • MSRV is now explicitly set in the package definition.
  • Replaced lazy_static with once_cell as once_cell::sync::Lazy is being standardized and lazy_static is not actively maintained anymore.
  • Added fuzzy-matcher as an optional dependency for fuzzy filtering in Select and MultiSelect prompts #​176
rust-lang/regex

v1.10.4

Compare Source

v1.10.3

Compare Source

===================
This is a new patch release that fixes the feature configuration of optional
dependencies, and fixes an unsound use of bounds check elision.

Bug fixes:

  • BUG #​1147:
    Set default-features=false for the memchr and aho-corasick dependencies.
  • BUG #​1154:
    Fix unsound bounds check elision.

v1.10.2

Compare Source

===================
This is a new patch release that fixes a search regression where incorrect
matches could be reported.

Bug fixes:

  • BUG #​1110:
    Revert broadening of reverse suffix literal optimization introduced in 1.10.1.

v1.10.1

Compare Source

===================
This is a new patch release with a minor increase in the number of valid
patterns and a broadening of some literal optimizations.

New features:

  • FEATURE 04f5d7be:
    Loosen ASCII-compatible rules such that regexes like (?-u:☃) are now allowed.

Performance improvements:

  • PERF 8a8d599f:
    Broader the reverse suffix optimization to apply in more cases.

v1.10.0

Compare Source

===================
This is a new minor release of regex that adds support for start and end
word boundary assertions. That is, \< and \>. The minimum supported Rust
version has also been raised to 1.65, which was released about one year ago.

The new word boundary assertions are:

  • \< or \b{start}: a Unicode start-of-word boundary (\W|\A on the left,
    \w on the right).
  • \> or \b{end}: a Unicode end-of-word boundary (\w on the left, \W|\z
    on the right)).
  • \b{start-half}: half of a Unicode start-of-word boundary (\W|\A on the
    left).
  • \b{end-half}: half of a Unicode end-of-word boundary (\W|\z on the
    right).

The \< and \> are GNU extensions to POSIX regexes. They have been added
to the regex crate because they enjoy somewhat broad support in other regex
engines as well (for example, vim). The \b{start} and \b{end} assertions
are aliases for \< and \>, respectively.

The \b{start-half} and \b{end-half} assertions are not found in any
other regex engine (although regex engines with general look-around support
can certainly express them). They were added principally to support the
implementation of word matching in grep programs, where one generally wants to
be a bit more flexible in what is considered a word boundary.

New features:

Performance improvements:

  • PERF #​1051:
    Unicode character class operations have been optimized in regex-syntax.
  • PERF #​1090:
    Make patterns containing lots of literal characters use less memory.

Bug fixes:

  • BUG #​1046:
    Fix a bug that could result in incorrect match spans when using a Unicode word
    boundary and searching non-ASCII strings.
  • BUG(regex-syntax) #​1047:
    Fix panics that can occur in Ast->Hir translation (not reachable from regex
    crate).
  • BUG(regex-syntax) #​1088:
    Remove guarantees in the API that connect the u flag with a specific HIR
    representation.

regex-automata breaking change release:

This release includes a regex-automata 0.4.0 breaking change release, which
was necessary in order to support the new word boundary assertions. For
example, the Look enum has new variants and the LookSet type now uses u32
instead of u16 to represent a bitset of look-around assertions. These are
overall very minor changes, and most users of regex-automata should be able
to move to 0.4 from 0.3 without any changes at all.

regex-syntax breaking change release:

This release also includes a regex-syntax 0.8.0 breaking change release,
which, like regex-automata, was necessary in order to support the new word
boundary assertions. This release also includes some changes to the Ast
type to reduce heap usage in some cases. If you are using the Ast type
directly, your code may require some minor modifications. Otherwise, users of
regex-syntax 0.7 should be able to migrate to 0.8 without any code changes.

regex-lite release:

The regex-lite 0.1.1 release contains support for the new word boundary
assertions. There are no breaking changes.

v1.9.6

Compare Source

==================
This is a patch release that fixes a panic that can occur when the default
regex size limit is increased to a large number.

  • BUG aa4e4c71:
    Fix a bug where computing the maximum haystack length for the bounded
    backtracker could result underflow and thus provoke a panic later in a search
    due to a broken invariant.
serde-rs/serde

v1.0.198

Compare Source

v1.0.197

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@kjuulh
Copy link
Owner Author

kjuulh commented Apr 19, 2024

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

@kjuulh kjuulh force-pushed the renovate/all branch 4 times, most recently from 9bd090b to a8c35a7 Compare April 23, 2024 04:20
@kjuulh kjuulh force-pushed the renovate/all branch 3 times, most recently from 2ae8f84 to 8be9bc5 Compare May 1, 2024 16:42
@kjuulh kjuulh force-pushed the renovate/all branch 4 times, most recently from 32b2d44 to 6e8ea35 Compare May 13, 2024 02:13
@kjuulh kjuulh force-pushed the renovate/all branch 8 times, most recently from afdd895 to f1ceee4 Compare May 18, 2024 15:00
@kjuulh kjuulh force-pushed the renovate/all branch 3 times, most recently from b055bcb to ed755a8 Compare August 23, 2024 21:11
@kjuulh kjuulh force-pushed the renovate/all branch 5 times, most recently from 5efb2f8 to 4fb84a8 Compare September 5, 2024 00:19
@kjuulh kjuulh force-pushed the renovate/all branch 4 times, most recently from 2e57297 to 70857dc Compare December 4, 2024 05:23
@kjuulh kjuulh force-pushed the renovate/all branch 6 times, most recently from f602fa2 to b4c9571 Compare December 10, 2024 05:24
@kjuulh kjuulh force-pushed the renovate/all branch 3 times, most recently from 6147d7b to 0abba9d Compare December 23, 2024 05:28
@kjuulh kjuulh force-pushed the renovate/all branch 7 times, most recently from da4753a to bd13765 Compare January 9, 2025 05:22
@kjuulh kjuulh force-pushed the renovate/all branch 4 times, most recently from a81cd14 to d9fab18 Compare January 15, 2025 05:28
@kjuulh kjuulh force-pushed the renovate/all branch 4 times, most recently from eafda5e to 6f01d76 Compare January 21, 2025 05:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant