fix(deps): update all dependencies #74
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/all"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
1.0.96->1.0.980.4.4->1.0.04.5.31->4.5.370.9.8->0.18.00.13.0->0.14.01.10.5->1.11.10.12.5->0.12.151.0.120->1.0.1400.7.4->0.8.01.43.0->1.44.20.5.2->0.6.01.9.1->1.16.0Release Notes
dtolnay/anyhow (anyhow)
v1.0.98Compare Source
self.into_boxed_dyn_error()andself.reallocate_into_boxed_dyn_error_without_backtrace()methods for anyhow::Error (#415)v1.0.97Compare Source
Xuanwo/backon (backon)
v1.5.0Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/Xuanwo/backon/compare/v1.4.1...v1.5.0
v1.4.1Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/Xuanwo/backon/compare/v1.4.0...v1.4.1
v1.4.0Compare Source
What's Changed
futures-timerby @NumberFour8 in https://github.com/Xuanwo/backon/pull/154New Contributors
Full Changelog: https://github.com/Xuanwo/backon/compare/v1.3.0...v1.4.0
v1.3.0Compare Source
What's Changed
adaptableby @Xuanwo in https://github.com/Xuanwo/backon/pull/155with_max_timesby @shikhar in https://github.com/Xuanwo/backon/pull/161New Contributors
Full Changelog: https://github.com/Xuanwo/backon/compare/v1.2.0...v1.3.0
v1.2.0Compare Source
no_std.What's Changed
New Contributors
Full Changelog: https://github.com/Xuanwo/backon/compare/v1.1.0...v1.2.0
v1.1.0Compare Source
A Letter to BackON Users
Hello everyone,
Thank you very much for using BackON!
Before releasing version
1.0.0, I thought it would be better to let users choose their own sleeper implementations, so I didn't enable them by default. However, many users encountered runtime panics. I apologize for not finding a solution that meets all requirements simultaneously: no API breaks, allowing sleeper passing at runtime, and no extra cost.So in version
1.1.0, I have addedtokio-sleeperandgloo-timers-sleepto thedefaultfeature. This change will make BackON behave like version0.4.4, allowing users to upgrade without adding new features. Additionally, I have moved the panic to occur earlier during thepollfeature instead of during thesleepcall. This makes it easier to catch issues during development rather than at runtime. Furthermore, we will only panic during thedebugprofile and do nothing in thereleaseprofile. This should protect users from panics even in the worst-case scenarios.Please let me know if you have better solutions! Thanks in advance!
Xuanwo
What's Changed
Full Changelog: https://github.com/Xuanwo/backon/compare/v1.0.2...v1.1.0
v1.0.2Compare Source
What's Changed
&mut selffunction by @Xuanwo in https://github.com/Xuanwo/backon/pull/118Full Changelog: https://github.com/Xuanwo/backon/compare/v1.0.1...v1.0.2
v1.0.1Compare Source
What's Changed
Full Changelog: https://github.com/Xuanwo/backon/compare/v1.0.0...v1.0.1
v1.0.0Compare Source
Upgrade
Since 1.0.0, backon Retry doesn't take a reference of builder anymore:
Since version 0.5.0, backon no longer directly depends on
tokio. Instead, users can now provide their own sleep implementation.For example:
To maintain the same behavior as before, please enable the
tokio-sleepfeature.What's Changed
Full Changelog: https://github.com/Xuanwo/backon/compare/v0.5.0...v1.0.0
v0.5.0Compare Source
Upgrade
Since version 0.5.0, backon no longer directly depends on
tokio. Instead, users can now provide their own sleep implementation.For example:
To maintain the same behavior as before, please enable the
tokio-sleepfeature.What's Changed
New Contributors
Full Changelog: https://github.com/Xuanwo/backon/compare/v0.4.4...v0.5.0
clap-rs/clap (clap)
v4.5.37Compare Source
Features
ArgMatches::try_clear_id()v4.5.36Compare Source
Fixes
v4.5.35Compare Source
Fixes
help_headingv4.5.34Compare Source
Fixes
flatten_help(true)and subcommands without argumentsv4.5.33Compare Source
Fixes
v4.5.32Compare Source
Features
Error::removeDocumentation
humantimetojiffInternal
pulldown-cmarkdagger/dagger (dagger-sdk)
v0.18.4Compare Source
Fixed
DirectoryandFileflags by @helderco in https://github.com/dagger/dagger/pull/10169CurrentModuleAPI during SDK module initialization by @sipsma in https://github.com/dagger/dagger/pull/10213llm.withModelfrom a module function by @sipsma in https://github.com/dagger/dagger/pull/10230.plaintexton a URI-based secret from a module w/ cache hit by @sipsma in https://github.com/dagger/dagger/pull/10223setSecretprovided empty plaintext value and passed between function calls by @sipsma in https://github.com/dagger/dagger/pull/10223Experimental
What to do next?
v0.18.3Compare Source
Added
--recursiveflag fordagger developby @jedevc in https://github.com/dagger/dagger/pull/9860Container.buildandDirectory.dockerBuildby @sipsma in https://github.com/dagger/dagger/pull/10088ttlfor local secret caching for vault by @rajatjindal in https://github.com/dagger/dagger/pull/9997Fixed
Experimental
What to do next?
v0.18.2Compare Source
Changed
with-execpositional arguments by @helderco in https://github.com/dagger/dagger/pull/10063Fixed
What to do next?
v0.18.1Compare Source
What to do next?
v0.18.0Compare Source
Changed
Fixed
What to do next?
v0.17.2Compare Source
Added
Directory.filterAPI for improved ergonomics by @rajatjindal in https://github.com/dagger/dagger/pull/9976This was previously possible by doing
Query.directory.withDirectory("", dir), but this breaks the chain.Changed
What to do next?
v0.17.1Compare Source
dag.Llm. To fix, simply change todag.LLMWhat to do next?
v0.17.0Compare Source
Added
Stabilized Dagger Shell by @helderco in https://github.com/dagger/dagger/pull/9896
Find out more at https://docs.dagger.io/features/shell/
New top-level
LLMAPI to allow integrating LLMs with native Dagger types in https://github.com/dagger/dagger/pull/9628Find out more at https://docs.dagger.io/ai-agents/
Changed
/run/dagger/engine.sockby @sipsma in https://github.com/dagger/dagger/pull/9866The previous socket path still exists for backwards compatibility but may be removed in a future version.
Directory.globandDirectory.entriesnow return a trailing slash to distinguish from regular files by @jedevc in https://github.com/dagger/dagger/pull/9118What to do next?
v0.16.3Compare Source
Added
Directory.asGitAPI for converting a directory into a git repository by @jedevc in https://github.com/dagger/dagger/pull/9730dagger callforGitRepositoryandGitReftypes by @jedevc in https://github.com/dagger/dagger/pull/9844Container.asTarballby @jedevc in https://github.com/dagger/dagger/pull/9395Changed
Dependencies
What to do next?
v0.16.2Compare Source
Added
Directory.namefield to retrieve current directory name by @TomChv in https://github.com/dagger/dagger/pull/9617Fixed
dagger callordagger functionscalled in directory with no modules - it now errors cleanly by @sipsma in https://github.com/dagger/dagger/pull/9658dagger.jsonby @sipsma in https://github.com/dagger/dagger/pull/9659Dependencies
What to do next?
v0.16.1Compare Source
Fixed
cannot sub-select 1th item from *dagql.PostCallTypedby @sipsma in https://github.com/dagger/dagger/pull/9634What to do next?
v0.16.0Compare Source
🔥 Breaking Changes
To match automatic configuration,
insecure-entitlementsnow includessecurity.insecurewhen configuring the engine manually by @jedevc in https://github.com/dagger/dagger/pull/9513Module load performance is improved and related API refactored by @sipsma in https://github.com/dagger/dagger/pull/9505
Loading of modules (the
load modulestep shown in progress output) is faster now in many cases. In particular:Users of modules with large numbers of dependencies or in large git repositories are expected to see the most immediate benefit.
For some concrete numbers, here are
load moduletimes for thedagger-dev's module in Dagger's repository under different scenarios:dagger call --helpon new engines with an empty cachedagger call --helpwith no file changes in the repo:dagger call --helpafter making a change to a random source code file in the repo:These improvements in cache utilization are also setup for future improvements not only in
load moduletimes but function call times more generally.This improvement comes with a few breaking changes that are not expected to impact most users. However, the changes require that users upgrade their CLI to v0.16.0 in order to connect to v0.16.0 engines. Older CLIs will error when connecting to newer engines.
In terms of the breaking changes, impacted users are those who:
They may need to update their dagger.json configuration file to add an explicit
"include"setting to ensure those extra files or directories are loaded with the module. This is because numerous files previously implicitly loaded are now skipped by default, which contributes to the performance improvements.For example, if your module code is in
.daggerand relies on thego.modfile in the parent directory, you would add the following to yourdagger.jsonfile:The values in the
"include"array are relative to the directory containingdagger.json. They can be also be glob patterns (e.g."**/*.txt"). To explicitly exclude some files matched by a previous include pattern, you can prepend the include pattern with a!character (e.g."!**/foo.txt").excludesetting existed but has now been superseded by prefixing an include pattern with a!character. However, this is backwards-compatible, so existingexcludesettings will be automatically turned into equivalent!-prefixed include settings when runningdagger develop. No user intervention is needed.The core API's
ModuleSourceandModuletypes have also undergone some cleanup that includes breaking changes. Most users do not interact with these APIs, but any that do may need some minor adjustments to their code. In particular:Module.initializeno longer needs to be called; the module is initialized on creationResolveFromCallerno longer needs to be called for local module sources; context is automatically loaded and resolved efficiently as needed by other API callsAdded
dag.Hostoperations by @jedevc in https://github.com/dagger/dagger/pull/9610What to do next?
v0.15.4Compare Source
Added
dagger.jsonsdkfield tosdk.sourceby @rajatjindal in https://github.com/dagger/dagger/pull/9454Fixed
What to do next?
v0.15.3Compare Source
Added
Note: the precision of float is limited to float64 inside the engine.
Fixed
Container.WithFilesby @jedevc in https://github.com/dagger/dagger/pull/9457Dependencies
What to do next?
v0.15.2Compare Source
Added
dagger updatecommand to update dependencies indagger.jsonby @rajatjindal in https://github.com/dagger/dagger/pull/8839$schemaproperty indagger.jsonby @JacobLey in https://github.com/dagger/dagger/pull/9069Changed
CacheVolumesare now namespaced between different modules by @rajatjindal in https://github.com/dagger/dagger/pull/8724CACHEDoperations for--progress=plainoutput by @marcosnils in https://github.com/dagger/dagger/pull/9344Fixed
AsServiceby @marcosnils in https://github.com/dagger/dagger/pull/9247Container.terminalby @jedevc in https://github.com/dagger/dagger/pull/9338Container.upbehaves as identically as possible toContainer.AsService.upby @jedevc in https://github.com/dagger/dagger/pull/9231dagger installalways inserts dependencies in the right order by @jedevc in https://github.com/dagger/dagger/pull/9052What to do next?
v0.15.1Compare Source
Fixed
What to do next?
v0.13.7Added
expectarg forContainer.withExecby @jedevc in https://github.com/dagger/dagger/pull/8466This enum arg allows specifying valid return statuses for which the command
can return without failing immediately.
Container.exitCodefield to get the exit code of the lastwithExecby @jedevc in https://github.com/dagger/dagger/pull/8466Changed
The new policies attempt to co-operate with other applications using the disk
and will adjust its cache usage accordingly.
Previously, when a function chain in
dagger callended in an object, we'dprint all functions that return a simple value and don't have any arguments.
Now, only object fields will be included, not all functions.
Fixed
withExecs using theExperimentalPrivilegedNestingflag by @sipsma in https://github.com/dagger/dagger/pull/8776What to do next?
v0.11.9Compare Source
Fixed
What to do next?
rust-itertools/itertools (itertools)
v0.14.0Compare Source
Breaking
cons_tuples(#988)Added
array_combinations(#991)k_smallest_relaxedand variants (#925)next_arrayandcollect_array(#560)DoubleEndedIteratorforFilterOk(#948)DoubleEndedIteratorforFilterMapOk(#950)Changed
Q: ?SizedinItertools::contains(#971)chain!(#943)into_group_map_bydocumentation (#1000)tree_reducedocumentation (#955)merge_join_by(#966)take_while_inclusive(#972)find_or_lastandfind_or_first(#984)tuple_combinations(#945)track_callerattr forasser_equal(#976)Notable Internal Changes
default_featuresinCargo.tomltodefault-features(#985)rust-lang/regex (regex)
v1.11.1Compare Source
===================
This is a new patch release of
regexthat fixes compilation on nightlyRust when the unstable
patterncrate feature is enabled. Users on nightlyRust without this feature enabled are unaffected.
Bug fixes:
Fix the
Patterntrait implementation as a result of nightly API breakage.v1.11.0Compare Source
===================
This is a new minor release of
regexthat brings in an update to theUnicode Character Database. Specifically, this updates the Unicode data
used by
regexinternally to the version 16 release.New features:
Add new
regex::SetMatches::matched_allmethod.Update to Unicode Character Database (UCD) version 16.
v1.10.6Compare Source
===================
This is a new patch release with a fix for the
unstablecrate feature thatenables
std::str::Patterntrait integration.Bug fixes:
Fix the
Patterntrait implementation as a result of nightly API breakage.seanmonstar/reqwest (reqwest)
v0.12.15Compare Source
ProxyOverrideandNO_PROXY.v0.12.14Compare Source
fetch_mode_no_cors(), marking as deprecated when not on WASM.v0.12.13Compare Source
Form::into_reader()for blockingmultipartforms.Form::into_stream()for asyncmultipartforms.RequestBuilder::form()from overwriting a previously setContent-Typeheader, like the other builder methods.blocking::Request.ProxyOverrideas aNO_PROXYvalue.Error::is_timeout()to return true when from a request timeout.v0.12.12Compare Source
tokio/timeon WASM.v0.12.11Compare Source
v0.12.10Compare Source
ClientBuilder::connector_layer()to allow customizing the connector stack.ClientBuilder::http2_max_header_list_size()option.content-length) information when wrapping bodies.v0.12.9Compare Source
tls::CertificateRevocationListssupport.connection_verbose()to output read logs.multipart::Part::file()to automatically include content-length.v0.12.8Compare Source
multipart::Form::file()method for adding files easily.Body::wrap()to wrap anyhttp_body::Bodytype.v0.12.7Compare Source
impl Service<http::Request<_>>forClient.v0.12.6Compare Source
danger_accept_invalid_hostnamesforrustls.impl Service<http::Request<Body>>forClientand&'_ Client.!Syncbodies inBody::wrap_stream().hickory-dnsis used.Proxyso thatHTTP(S)_PROXYvalues take precedence overALL_PROXY.blocking::RequestBuilder::header()from unsettingsensitiveon passed header values.serde-rs/json (serde_json)
v1.0.140Compare Source
v1.0.139Compare Source
v1.0.138Compare Source
v1.0.137Compare Source
v1.0.136Compare Source
v1.0.135Compare Source
v1.0.134Compare Source
RawValueassociated constants for literalnull,true,false(#1221, thanks @bheylin)v1.0.133Compare Source
v1.0.132Compare Source
v1.0.131Compare Source
Map<String, Value>and&Map<String, Value>(#1135, thanks @swlynch99)v1.0.130Compare Source
Numberfrom i128 and u128 (#1141, thanks @druide)v1.0.129Compare Source
serde_json::Map::sort_keysandserde_json::Value::sort_all_objects(#1199)v1.0.128Compare Source
v1.0.127Compare Source
v1.0.126Compare Source
v1.0.125Compare Source
v1.0.124Compare Source
v1.0.123Compare Source
v1.0.122Compare Source
json!in no-std crates (#1166)v1.0.121Compare Source
launchbadge/sqlx (sqlx)
v0.8.5Hotfix release to address two new issues:
sqlx-cli@0.8.4broke.envdefault resolution mechanismsqlx@0.8.4broke test fixture setupThe
0.8.4release will be yanked as of publishing this one.Added
sqlx-clinow accepts--no-dotenvin subcommand arguments.sqlx-clito CI.#[sqlx::test]twice in CI to cover cleanup.Fixed
sqlx-clicorrectly reads.envfiles by default again.#[sqlx::test].v0.8.450 pull requests were merged this release cycle.
As of this release, development of
0.9.0has begun onmain.Barring urgent hotfixes, this is expected to be the last release of
0.8.x.Added
push_valuesis passed an empty set of tuples [[@chanmaoganda]]transaction_depththroughget_transaction_depth()method [[@mpyw]]Connection::is_in_transactionin [#3765]begin_withmethods to support database-specific transaction options [[@bonsairobo]]Changed
#[track_caller]toRow::get()[[@karambarakat]]futures-core/futures-utilAPIs withstdvariants [[@paolobarbolini]]Fixed
SQLITE_OPEN_URIon in-memory sqlite [[@LecrisUT]]PgCopyIn[[@joeydewaal]]CARGO_MANIFEST_DIR[[@joeydewaal]]limit: 0for allExecutemessagesCertificateInput::frominfer any PEM-encoded documentPGSSLKEYnot being parsed correctly when containing a PEM-encoded private key.PgConnectOptionsPGHOSTADDRnow can be used to overridePGHOST.v0.8.3Compare Source
41 pull requests were merged this release cycle.
Added
Uuidanduuid::fmt::Hyphenated[[@abonander]]Changed
.pgpassfile warning to a debug message. [[@denschub]]PgListener::try_recv[[@swlynch99]]UNION ALLinstead ofUNIONin nullable check [[@Suficio]]Fixed
no-transactionflag in down migrations [[@manifest]]sqlformat[[@tbar4]]query_as[[@xuehaonan27]]INTERVAL[][[@Ddystopia]]EXPLAINin nullability check for QuestDB [[@Suficio]]v0.8.2Compare Source
10 pull requests were merged this release cycle.
This release addresses a few regressions that have occurred, and refines SQLx's MSRV policy (see the FAQ).
Added
Changed
Cargo.tomlfiles in examples [[@carschandler]]Fixed
#[sqlx(no_pg_array)]being forbidden on#[derive(Type)]structs.PgListener,PgStream::recv()[[@abonander]]unknown message: "\\0"errorv0.8.1Compare Source
16 pull requests were merged this release cycle.
This release contains a fix for RUSTSEC-2024-0363.
Postgres users are advised to upgrade ASAP as a possible exploit has been demonstrated:
#3440 (comment)
MySQL and SQLite do not appear to be exploitable, but upgrading is recommended nonetheless.
Added
MySqlConnectOptions::no_engine_substitution()[[@kolinfluence]]MySqlConnectOptions::no_engine_subsitution()(oops) in favor of the correctly spelled version.Changed
spec_errormodule [[@abonander]]Use at your own risk.
libsqlite3-sys=0.30.1to support sqlite 3.46 [[@CommanderStorm]]ring(the existing implementation),and
aws-lc-rswhich has optional FIPS certification.runtime-tokio-rustls,runtime-async-std-rustls,tls-rustls)enable the
ringprovider of RusTLS to match the existing behavior so this should not be a breaking change.tls-rustls-aws-lc-rsfeature to use theaws-lc-rsprovider.runtime-tokio-rustlsorruntime-async-std-rustls,this will necessitate switching to the appropriate non-legacy runtime feature:
runtime-tokioorruntime-async-stdFixed
sqlx::Type[[@alu]]node12inSQLxaction [[@hamirmahal]]v0.18.1to avoid yankedv0.14.3[[@CommanderStorm]]v0.8.0Compare Source
70 pull requests were merged this release cycle.
#2697 was merged the same day as release 0.7.4 and so was missed by the automatic CHANGELOG generation.
Breaking
#[sqlx::test]usages are applied in the correct order now.MigrateError.-- no-transactionto the beginning.Migrationi64as intermediate when decoding [[@abonander]]#[derive(sqlx::Type)]in Postgres [[@abonander]]#[sqlx(no_pg_array)]where conflicts occur.PgTypeInfo::with_name()infers types that start with_to be arrays of the un-prefixed type. Wrap type names in quotes to bypass this behavior.FromRow, returnError::ColumnDecodeforTryFromerrors [[@abonander]]#[sqlx(try_from = "T")]now returnError::ColumnDecodeinstead ofError::ColumnNotFound.#[sqlx(default)]on an individual field or the struct itself would have previously suppressed the error.This doesn't seem like good behavior as it could result in some potentially very difficult bugs.
Fromand apply the default explicitly.#[sqlx(rename)]and#[sqlx(rename_all)]to match the expected behavior (renamewins).ConnectOptions::to_url_lossy()to match what parsing expects.Added
MySqlTime, auditmysql::typesfor panics [[@abonander]]NonZero*scalar types [[@AlphaKeks]]Changed
Sendtrait bound from argument binding [[@bobozaur]]libsqlite3-sysare not considered breaking changes as per our semver guarantees.MySqlConnectionto reduce sizes of futures [[@stepantubanov]]sqlx migrate add ...[[@CommanderStorm]]Fixed
ConnectionHandleRawtype [[@abonander]]docker composeinstead ofdocker-compose[[@abonander]]pathownership problems when usingsqlx_macros_unstable[[@lily-mosquitoes]]sqlx_postgres::any[[@Zarathustra2]]migrateerror message. (#3275) [[@nk9]]persistentquery setting when preparing queries with theAnydriver [[@etorreborre]]select_input_type!()being unhygenic [[@CommanderStorm]]MorCNotice fields are not UTF-8 [[@YgorSouza]]json-feature should activatesqlx-postgres?/jsonas well [[@CommanderStorm]]clockandstdfeatures ofworkspace.dependencies.chrono.tokio-rs/tokio (tokio)
v1.44.2: Tokio v1.44.2Compare Source
This release fixes a soundness issue in the broadcast channel. The channel
accepts values that are
Sendbut!Sync. Previously, the channel calledclone()on these values without synchronizing. This release fixes the channelby synchronizing calls to
.clone()(Thanks Austin Bonander for finding andreporting the issue).
Fixed
clone()call in broadcast channel (#7232)v1.44.1: Tokio v1.44.1Compare Source
1.44.1 (March 13th, 2025)
Fixed
block_in_placecontext (#7216)v1.44.0: Tokio v1.44.0Compare Source
1.44.0 (March 7th, 2025)
This release changes the
from_stdmethod on sockets to panic if a blocking socket is provided. We determined this change is not a breaking change as Tokio is not intended to operate using blocking sockets. Doing so results in runtime hangs and should be considered a bug. Accidentally passing a blocking socket to Tokio is one of the most common user mistakes. If this change causes an issue for you, please comment on #7172.Added
task::coopmodule (#7116)Command::get_kill_on_drop()(#7086)broadcast::Sender::closed(#6685, #7090)broadcast::WeakSender(#7100)oneshot::Receiver::is_empty()(#7153)oneshot::Receiver::is_terminated()(#7152)Fixed
Fileshould not start a background read (#7139)start_killon exited child should not fail (#7160)CTRL_CLOSE,CTRL_LOGOFF,CTRL_SHUTDOWNon windows (#7122)Changes
select!budget-aware (#7164)from_std(#7166)Changes to unstable APIs
Documented
select!alternatives (#7110)send_to(#7146)Childstdout (#7141)Child::killbehavior (#7162)ChildStdinstruct doc comment (#7192)worker_threadsinstead ofcore_threads(#7186)v1.43.1Compare Source
tower-rs/tower-http (tower-http)
v0.6.2Compare Source
Changed:
CompressionBody<B>now propagatesB's size hint in itshttp_body::Bodyimplementation, if compression is disabled (#531)
content-lengthto be included in an HTTP message with thisbody for those cases
New Contributors
Full Changelog: https://github.com/tower-rs/tower-http/compare/tower-http-0.6.1...tower-http-0.6.2
v0.6.1: v0.6.1Compare Source
Fixed
New Contributors
v0.6.0: v0.6.0Compare Source
Changed:
bodymodule is disabled except forcatch-panic,decompression-*,fs, orlimitfeatures (BREAKING) (#477)tower0.5 (#503)Fixed
uuid-rs/uuid (uuid)
v1.16.0Compare Source
What's Changed
Uuid::new_v8const by @tguichaoua in https://github.com/uuid-rs/uuid/pull/815New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/v1.15.1...v1.16.0
v1.15.1Compare Source
What's Changed
Full Changelog: https://github.com/uuid-rs/uuid/compare/v1.15.0...v1.15.1
v1.15.0Compare Source
What's Changed
Debugimplementation for NonNilUUid by @rick-de-water in https://github.com/uuid-rs/uuid/pull/808New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/v1.14.0...v1.15.0
v1.14.0Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/v1.13.2...v1.14.0
v1.13.2Compare Source
What's Changed
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.13.1...v1.13.2
v1.13.1Compare Source
What's Changed
wasm32withatomicsby @bushrat011899 in https://github.com/uuid-rs/uuid/pull/797New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.13.0...1.13.1
v1.13.0Compare Source
⚠️ Potential Breakage
This release updates our version of
getrandomto0.3andrandto0.9. It is a potentially breaking change for the following users:no-std users who enable the
rngfeatureuuidstill usesgetrandomby default on these platforms. Upgrade your version ofgetrandomand follow its new docs on configuring a custom backend.wasm32-unknown-unknownusers who enable therngfeature without thejsfeatureUpgrade your version of
getrandomand follow its new docs on configuring a backend.You'll also need to enable the
rng-getrandomorrng-randfeature ofuuidto force it to usegetrandomas its backend:If you're on
wasm32-unknown-unknownand using thejsfeature ofuuidyou shouldn't see any breakage. We've kept this behavior by vendoring ingetrandom's web-based backend when thejsfeature is enabled.What's Changed
getrandomto0.3andrandto0.9by @KodrAus in https://github.com/uuid-rs/uuid/pull/793getrandomonwasm32-unknown-unknownwithout JavaScript by @KodrAus in https://github.com/uuid-rs/uuid/pull/794Full Changelog: https://github.com/uuid-rs/uuid/compare/1.12.1...1.13.0
v1.12.1Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.12.0...1.12.1
v1.12.0Compare Source
⚠️ Possible Breakage
This release includes additional
PartialEqimplementations onUuid, which can break inference in some cases.What's Changed
NonZeroUuidtype for optimizedOption<Uuid>representation by @ab22593k in https://github.com/uuid-rs/uuid/pull/779NonNilUuidby @KodrAus in https://github.com/uuid-rs/uuid/pull/783New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.11.1...1.12.0
v1.11.1Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.11.0...1.11.1
v1.11.0Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.10.0...1.11.0
v1.10.0Compare Source
Deprecations
This release deprecates and renames the following functions:
Builder::from_rfc4122_timestamp->Builder::from_gregorian_timestampBuilder::from_sorted_rfc4122_timestamp->Builder::from_sorted_gregorian_timestampTimestamp::from_rfc4122->Timestamp::from_gregorianTimestamp::to_rfc4122->Timestamp::to_gregorianWhat's Changed
New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.9.1...1.10.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.
e3568a8101to6f4132691efix(deps): update all dependenciesto chore(deps): update all dependencies6f4132691eto6eeba20474chore(deps): update all dependenciesto fix(deps): update all dependencies6eeba20474tofd3becace7fd3becace7toc43367b32dc43367b32dtocc0eb56a97cc0eb56a97tof0174cd03df0174cd03dtoad66c52551ad66c52551to4d8f62c8ca4d8f62c8catoc90c6cb514c90c6cb514toe47a49cdace47a49cdactoe59f14f41ee59f14f41etoc8cfd3e7dfc8cfd3e7dftoa5e5f3c619a5e5f3c619to3526a5f9563526a5f956to2b40ed4a3eCheckout
From your project repository, check out a new branch and test the changes.