chore(deps) Update Tauri Codegen (1.x) - abandoned #10721

renovate · 2024-08-21T16:52:50Z

This PR contains the following updates:

Package	Type	Update	Change
base64	dependencies	minor	`0.21` -> `0.22`
plist	dependencies	minor	`1.5.1` -> `1.7.0`
regex	dependencies	minor	`1.9.6` -> `1.10.6`
semver	dependencies	patch	`1.0.22` -> `1.0.23`
serde (source)	dependencies	patch	`1.0.198` -> `1.0.208`
serde_json	dependencies	patch	`1.0.97` -> `1.0.125`
thiserror	dependencies	patch	`1.0.59` -> `1.0.63`
time (source)	dependencies	patch	`0.3.15` -> `0.3.36`
uuid	dependencies	minor	`1.8.0` -> `1.10.0`

Release Notes

marshallpierce/rust-base64 (base64)

`v0.22.1`

Compare Source

Correct the symbols used for the predefined alphabet::BIN_HEX.

`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%)

ebarnard/rust-plist (plist)

rust-lang/regex (regex)

`v1.10.6`

Compare Source

===================
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:
Fix the Pattern trait implementation as a result of nightly API breakage.

`v1.10.5`

Compare Source

===================
This is a new patch release with some minor fixes.

Bug fixes:

BUG #1203:
Escape invalid UTF-8 when in the Debug impl of regex::bytes::Match.

`v1.10.4`

Compare Source

===================
This is a new patch release with some minor fixes.

BUG #1169:
Fixes a bug with compiling a reverse NFA automaton in regex-automata.
BUG #1178:
Clarifies that when Cow::Borrowed is returned from replace APIs, it is
equivalent to the input.

`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:

FEATURE #469:
Add support for \< and \> word boundary assertions.
FEATURE(regex-automata) #1031:
DFAs now have a start_state method that doesn't use an Input.

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.

dtolnay/semver (semver)

`v1.0.23`

Compare Source

Resolve unexpected_cfgs warning (#318)

serde-rs/serde (serde)

`v1.0.208`

Compare Source

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

`v1.0.207`

Compare Source

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

`v1.0.206`

Compare Source

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

`v1.0.205`

Compare Source

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)

`v1.0.204`

Compare Source

Apply #[diagnostic::on_unimplemented] attribute on Rust 1.78+ to suggest adding serde derive or enabling a "serde" feature flag in dependencies (#2767, thanks @weiznich)

`v1.0.203`

Compare Source

Documentation improvements (#2747)

`v1.0.202`

Compare Source

Provide public access to RenameAllRules in serde_derive_internals (#2743)

`v1.0.201`

Compare Source

Resolve unexpected_cfgs warning (#2737)

`v1.0.200`

Compare Source

Fix formatting of "invalid type" and "invalid value" deserialization error messages containing NaN or infinite floats (#2733, thanks @jamessan)

`v1.0.199`

Compare Source

Fix ambiguous associated item when forward_to_deserialize_any! is used on an enum with Error variant (#2732, thanks @aatifsyed)

serde-rs/json (serde_json)

`v1.0.125`

Compare Source

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

`v1.0.124`

Compare Source

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

`v1.0.123`

Compare Source

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`

Compare Source

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

`v1.0.121`

Compare Source

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

`v1.0.120`

Compare Source

Correctly specify required version of indexmap dependency (#1152, thanks @cforycki)

`v1.0.119`

Compare Source

Add serde_json::Map::shift_insert (#1149, thanks @joshka)

`v1.0.118`

Compare Source

Implement Hash for serde_json::Value (#1127, thanks @edwardycl)

`v1.0.117`

Compare Source

Resolve unexpected_cfgs warning (#1130)

`v1.0.116`

Compare Source

Make module structure comprehensible to static analysis (#1124, thanks @mleonhard)

`v1.0.115`

Compare Source

Documentation improvements

`v1.0.114`

Compare Source

Fix unused_imports warnings when compiled by rustc 1.78

`v1.0.113`

Compare Source

Add swap_remove and shift_remove methods on Map (#1109)

`v1.0.112`

Compare Source

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

`v1.0.111`

Compare Source

Improve floating point parsing performance on loongarch64 (#1100, thanks @heiher)

`v1.0.110`

Compare Source

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

`v1.0.109`

Compare Source

Documentation improvements

`v1.0.108`

Compare Source

Documentation improvements (#1075, #1081, #1082, thanks @dimo414 and @fritzrehde)

`v1.0.107`

Compare Source

impl IntoDeserializer for &RawValue (#1071)

`v1.0.106`

Compare Source

Add Value::as_number accessor (#1069, thanks @chanced)
Add Number::as_str accessor under "arbitrary_precision" feature (#1067, thanks @chanced)

`v1.0.105`

Compare Source

Support bool in map keys (#1054)

`v1.0.104`

Compare Source

Provide IntoDeserializer impl for &serde_json::Value (#1045, thanks @ZetaNumbers)

`v1.0.103`

Compare Source

Documentation improvements

`v1.0.102`

Compare Source

Add a way to customize the serialization of byte arrays (#1039)

`v1.0.101`

Compare Source

Allow f32 and f64 as keys in maps (#1027, thanks @overdrivenpotato)

`v1.0.100`

Compare Source

Support -Z minimal-versions

`v1.0.99`

Compare Source

Support serializing serde's option type in a map key (#1030, thanks @LPGhatguy)

`v1.0.98`

Compare Source

Update indexmap dependency used by "preserve_order" feature to version 2

dtolnay/thiserror (thiserror)

`v1.0.63`

Compare Source

Documentation improvements

`v1.0.62`

Compare Source

Support referring to nested tuple struct fields inside #[error("…", …)] attribute (#309)

`v1.0.61`

Compare Source

Use core::fmt and core::panic to facilitate error_in_core support (#299, thanks @jordens)

`v1.0.60`

Compare Source

Resolve unexpected_cfgs warning (#298)

time-rs/time (time)

`v0.3.36`

Compare Source

# Fixed

FormatItem can be used as part of an import path. See #675 for details.

`v0.3.35`

Compare Source

Added

Duration::checked_neg
ext::InstantExt, which provides methods for using time::Duration with std::time::Instant

Changed

Instant is deprecated. It is recommended to use std::time::Instant directly, importing
time::ext::InstantExt for interoperability with time::Duration.
FormatItem has been renamed to BorrowedFormatItem, avoiding confusion with OwnedFormatItem.
An alias has been added for backwards compatibility.

Fixed

The weekday is optional when parsing RFC2822.
The range of sub-second values in Duration is documented correctly. The previous documentation
contained an off-by-one error.
Leap seconds are now correctly handled when parsing ISO 8601.

`v0.3.34`

Compare Source

Fixed

Computing the local offset on Windows works again. It was broken in some cases in v0.3.32 and
v0.3.33.

`v0.3.33`

Compare Source

Fixed

Builds targeting wasm32-unknown-unknown now work again.

`v0.3.32`

Compare Source

Added

Methods to replace the day of the year.
- Date::replace_ordinal
- PrimitiveDateTime::replace_ordinal
- OffsetDateTime::replace_ordinal
Modules to treat an OffsetDateTime as a Unix timestamp with subsecond precision for serde.
- time::serde::timestamp::milliseconds
- time::serde::timestamp::microseconds
- time::serde::timestamp::nanoseconds

Changed

Duration::time_fn is deprecated.

`v0.3.31`

Compare Source

Added

OffsetDateTime::new_in_offset
OffsetDateTime::new_utc

Changed

The valid range of UtcOffset has been expanded from ±23:59:59 to ±25:59:59. This is to support
the full POSIX range while permitting infallible negation.

`v0.3.30`

Compare Source

Added

powerfmt::smart_display::SmartDisplay has been added for the main types in the library. These
implementations ensure that values follow the requested fill, width, and alignment when using
format! or similar macros. Display is implemented in terms of SmartDisplay.

Fixed

Large values no longer wrap around in release mode when using NumericalDuration or
NumericalStdDuration.

`v0.3.29`

Compare Source

Added

Niche value optimization for Date has been added. Both Date and Option<Date> are four bytes.
Unit conversions have been added. It is now possible to write Second::per(Day), which returns
the number of seconds in one day. See the types in the [time::convert module][time::convert module] for more
information.

Changed

The diagnostic for --cfg unsound_local_offset has been removed.
#![feature(no_coverage)] was previously used internally for code coverage. It is no longer used,
so it has been removed.
The default value for modifier::OffsetHour has been changed. This was unintentionally changed in
v0.3.17 and went unnoticed until now. The sign is now only present if needed by default, as was
the case previously. This does not affect any situation where format_description! or
format_description::parse is used.

Fixed

Adding or subtracting a std::time::Duration to/from an OffsetDateTime will not result in
integer overflow internally. It will still panic if the result is out of range.

`v0.3.28`

Compare Source

Added

More additional constants for the well-known Iso8601 format description have been added. This
avoids the need to manually configure the format.
An [end] component has been added. This is ignored during formatting, but is used to indicate
the end of input when parsing. If any input remains after this component, an error is returned.
This is useful when using the [first] component, as it avoids the need to reorder variants.

Changed

The exemption for MacOS introduced in 0.3.20 has been removed. This is because some supported
versions of MacOS do not meet the requirements for the exemption.
The UnexpectedTrailingCharacters error variant has been moved to ParseFromDescription. All
previously-existing locations of this variant have been deprecated and will no longer be returned.

`v0.3.27`

Compare Source

This sets the serde dependency requirement to >= 1.0.184 where the binaries have been removed.

`v0.3.26`

Compare Source

This release contains only a single change. serde is required to be a version prior to 1.0.171.
This is due to the decision by the maintainer of serde to include pre-built binaries that are
executed without the end user's knowledge. As of the time of publishing, the included binary has not
even been reproduced. This is a security risk, and the time project strongly opposes this
decision. While this may break some users' builds due to conflicting versions, it is a necessary
step to ensure the security.

`v0.3.25`

Compare Source

Fixed

Methods such as Time::replace_milliseconds would panic on some out-of-range values. This has
been fixed.

`v0.3.24`

Compare Source

Added

The subsecond component is taken into account when parsing the unix_timestamp component. If
data is conflicting, the subsecond value takes precedence.
Parsing a Time with only the hour component is now supported. The minute and second, and
subsecond components are assumed to be zero.

Changed

The minimum supported Rust version is now 1.67.0.
The debug output for Parsed has been improved.
When parsing, invalid values are now rejected sooner. Previously, the entire input would be parsed
before being rejected in the final step. Now, invalid values are rejected as soon as they are
encountered. This affects the error variant returned, which may cause minor breakage for any code
(incorrectly) relying on the exact error variant.
When parsing a Time, an error is returned if components are present but not consecutive. For
example, if hours and seconds are present, minutes will not be assumed to be zero.

Fixed

The implementation of Duration::checked_div could return a slightly incorrect result in some
cases. This has been fixed.

`v0.3.23`

Compare Source

Added

Date::next_occurrence
Date::prev_occurrence
Date::nth_next_occurrence
Date::nth_prev_occurrence
Weekday::nth_prev
Month::nth_next
Month::nth_prev

Changed

The minimum supported Rust version policy has been updated. See the README for
details.

Fixed

Duration::abs correctly returns Duration::MAX when near the minimum value. The nanoseconds
value was previously incorrect.
Compliance with ISO 8601 has been improved. Previously, a UTC offset would be incorrectly rejected
in some cases.

`v0.3.22`

Compare Source

Added

OffsetDateTime::checked_to_offset

`v0.3.21`

Compare Source

Added

Any formattable/parsable type can now be used with the time::serde::format_description! macro.
Weekday::nth_next

Changed

The minimum supported Rust version is now 1.65.0.

`v0.3.20`

Compare Source

Changed

The minimum supported Rust version is now 1.63.0.
On Unix-based operating systems with known thread-safe environments, functions obtaining the local
offset no longer require a check that the program is single-threaded. This currently includes
MacOS, illumos, and NetBSD.

Added

[ignore] component in format descriptions. A count modifier is required, indicating the number
of bytes to ignore when parsing.
[unix_timestamp] component in format descriptions. This is currently only usable with
OffsetDateTime. Users can choose between seconds, milliseconds, microseconds, and nanoseconds,
and whether the sign is mandatory or optional.

Fixed

The API for declaring soundness now uses stricter atomic orderings internally.

`v0.3.19`

Compare Source

Fixed

This includes the update to the format_description! macro, which was supposed to be included in
0.3.18.

`v0.3.18`

Compare Source

Changed

The minimum supported Rust version is now 1.62.0.

Added

[first] and [optional] items can now be included in format descriptions. To parse this at
runtime, you must use the format_description::parse_owned method.
format_description::parse_borrowed
An API has been added to opt out of soundness checks for obtaining the local offset. This replaces
the previous, officially unsupported RUSTFLAGS="--cfg unsound_local_offset". End users may call
time::util::local_offset::set_soundness(time::util::local_offset::Soundness::Unsound). This
method is unsafe because it enables undefined behavior if its safety requirements are not
upheld. Note that libraries must not set this to Unsound, as it is impossible for a library
to guarantee end users uphold the required invariants.

Fixed

Correctly parse offset sign when hour is zero. The parse was previously unconditionally positive,
even if the sign indicated otherwise.
Compilation is fixed for WebAssembly.

`v0.3.17`

Compare Source

Changed

The amount of code generated by time::serde::format_description! is reduced if not all feature
flags are active.
cargo test --tests works with any configuration of feature flags. This occurs by spawning a
subprocess that passes --all-features. cargo test --doc works with most combinations of
feature flags, including the default. The combination of these changes means that crater will now
run on time.
libc and num_threads are only included as dependencies when needed. They were previously
unconditionally included.

Added

time::format_description::parse_owned, which returns an OwnedFormatItem. This avoids "lifetime
hell", where all your structs now need a lifetime because a single field has one. Note that when
possible, the borrowed format item (just called FormatItem) is still preferred, as it has
significantly fewer allocations. The new OwnedFormatItem is usable for both formatting and
parsing, as you would expect.

Compatibility

The parser for runtime format descriptions has been rewritten. A side effect of this is that some
errors have slightly changed. No existing API has been altered, so this is not a breaking change.
However, you may notice different errors, which are hopefully better! The parser for compile-time
format descriptions has not yet been swapped out. If you notice any bugs, please file an issue.

`v0.3.16`

Compare Source

Changed

The minimum supported Rust version is now 1.60.0.
The serde-well-known feature flag is deprecated. The necessary features for an item to be
enabled are indicated in documentation.
Feature gates have been loosened for well-known formats.

Added

consts can now be provided as the format description for time::serde::format_description!. The
const must be of type &[FormatItem<'_>], which is what is returned by the
time::macros::format_description! macro.
```
const TIME_FORMAT_ALT: &[FormatItem<'_>] = time::macros::format_description!("[hour]:[minute]");
time::serde::format_description!(time_format_alt, Time, TIME_FORMAT_ALT);
```

Compatibility

Some feature flags have been removed. None of these have ever been documented as flags, so any use
was unsupported. These flags are:
- js-sys
- quickcheck-dep
- itoa
- time-macros

uuid-rs/uuid (uuid)

`v1.10.0`

Compare Source

Deprecations

This release deprecates and renames the following functions:

Builder::from_rfc4122_timestamp -> Builder::from_gregorian_timestamp
Builder::from_sorted_rfc4122_timestamp -> Builder::from_sorted_gregorian_timestamp
Timestamp::from_rfc4122 -> Timestamp::from_gregorian
Timestamp::to_rfc4122 -> Timestamp::to_gregorian

What's Changed

Use const identifier in uuid macro by @Vrajs16 in https://github.com/uuid-rs/uuid/pull/764
Rename most methods referring to RFC4122 by @Mikopet / @KodrAus in https://github.com/uuid-rs/uuid/pull/765
prepare for 1.10.0 release by @KodrAus in https://github.com/uuid-rs/uuid/pull/766

New Contributors

@Vrajs16 made their first contribution in https://github.com/uuid-rs/uuid/pull/764

Full Changelog: uuid-rs/uuid@1.9.1...1.10.0

`v1.9.1`

Compare Source

What's Changed

Add an example of generating bulk v7 UUIDs by @KodrAus in https://github.com/uuid-rs/uuid/pull/761
Avoid taking the shared lock when getting usable bits in Uuid::now_v7 by @KodrAus in https://github.com/uuid-rs/uuid/pull/762
Prepare for 1.9.1 release by @KodrAus in https://github.com/uuid-rs/uuid/pull/763

Full Changelog: uuid-rs/uuid@1.9.0...1.9.1

`v1.9.0`

Compare Source

`Uuid::now_v7()` is guaranteed to be monotonic

Before this release, Uuid::now_v7() would only use the millisecond-precision timestamp for ordering. It now also uses a global 42-bit counter that's re-initialized each millisecond so that the following will always pass:

let a = Uuid::now_v7();
let b = Uuid::now_v7();

assert!(a < b);

What's Changed

Add a get_node_id method for v1 and v6 UUIDs by @KodrAus in https://github.com/uuid-rs/uuid/pull/748
Update atomic and zerocopy to latest by @KodrAus in https://github.com/uuid-rs/uuid/pull/750
Add repository field to uuid-macro-internal crate by @paolobarbolini in https://github.com/uuid-rs/uuid/pull/752
update docs to updated RFC (from 4122 to 9562) by @Mikopet in https://github.com/uuid-rs/uuid/pull/753
Support counters in v7 UUIDs by @KodrAus in https://github.com/uuid-rs/uuid/pull/755

New Contributors

@paolobarbolini made their first contribution in https://github.com/uuid-rs/uuid/pull/752
@Mikopet made their first contribution in https://github.com/uuid-rs/uuid/pull/753

Full Changelog: uuid-rs/uuid@1.8.0...1.9.0

Configuration

📅 Schedule: Branch creation - "after 3am on Wednesday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, 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 was generated by Mend Renovate. View the repository job log.

renovate · 2024-08-21T16:52:52Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path core/tauri-codegen/Cargo.toml --package [email protected] --precise 0.22.1
    Updating crates.io index
error: failed to select a version for the requirement `base64 = "^0.21"`
candidate versions found which didn't match: 0.22.1
location searched: crates.io index
required by package `reqwest v0.11.18`
    ... which satisfies dependency `reqwest = "^0.11"` (locked to 0.11.18) of package `tauri v1.7.1 (/tmp/renovate/repos/github/tauri-apps/tauri/core/tauri)`

github-actions · 2024-08-21T16:58:48Z

Package Changes Through `a044d90`

There are 9 changes which include tauri with patch, tauri-codegen with patch, tauri-bundler with patch, tauri-cli with patch, @tauri-apps/cli with patch, tauri-runtime-wry with patch, tauri-utils with patch, tauri-build with patch, tauri-runtime with patch

Planned Package Versions

The following package releases are the planned based on the context of changes in this pull request.

package	current	next
tauri-utils	1.6.0	1.6.1
tauri-bundler	1.6.0	1.6.1
tauri-runtime	0.14.4	0.14.5
tauri-runtime-wry	0.14.9	0.14.10
tauri-codegen	1.4.4	1.4.5
tauri-macros	1.4.5	1.4.6
tauri-build	1.5.3	1.5.4
tauri	1.7.1	1.7.2
@tauri-apps/cli	1.6.0	1.6.1
tauri-cli	1.6.0	1.6.1

Add another change file through the GitHub UI by following this link.

Read about change files or the docs at github.com/jbolda/covector

renovate · 2024-08-27T21:43:11Z

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

chore(deps) Update Tauri Codegen

a044d90

renovate bot requested a review from a team as a code owner August 21, 2024 16:52

renovate bot added the type: chore label Aug 21, 2024

renovate bot changed the title ~~chore(deps) Update Tauri Codegen (1.x)~~ chore(deps) Update Tauri Codegen (1.x) - abandoned Aug 27, 2024

FabianLars closed this Sep 2, 2024

FabianLars deleted the renovate/1.x-alltauricodegen branch September 2, 2024 09:52

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps) Update Tauri Codegen (1.x) - abandoned #10721

chore(deps) Update Tauri Codegen (1.x) - abandoned #10721

renovate bot commented Aug 21, 2024

renovate bot commented Aug 21, 2024

github-actions bot commented Aug 21, 2024

renovate bot commented Aug 27, 2024

chore(deps) Update Tauri Codegen (1.x) - abandoned #10721

chore(deps) Update Tauri Codegen (1.x) - abandoned #10721

Conversation

renovate bot commented Aug 21, 2024

Release Notes

# Fixed

Added

Changed

Fixed

Fixed

Fixed

Added

Changed

Added

Changed

Added

Fixed

Added

Changed

Fixed

Added

Changed

Fixed

Added

Changed

Fixed

Added

Changed

Fixed

Added

Added

Changed

Changed

Added

Fixed

Fixed

Changed

Added

Fixed

Changed

Added

Compatibility

Changed

Added

Compatibility

Deprecations

What's Changed

New Contributors

What's Changed

Uuid::now_v7() is guaranteed to be monotonic

What's Changed

New Contributors

Configuration

renovate bot commented Aug 21, 2024

⚠️ Artifact update problem

File name: Cargo.lock

github-actions bot commented Aug 21, 2024

Package Changes Through a044d90

renovate bot commented Aug 27, 2024

Autoclosing Skipped

`Uuid::now_v7()` is guaranteed to be monotonic

Package Changes Through `a044d90`