Releases: Noelware/azalia
Releases · Noelware/azalia
v0.1.5
v0.1.4
- [azalia] Add config+tracing Cargo crate feature
Full Changelog: 0.1.3...0.1.4
v0.1.3
- Update tokio crate to v1.44.2
- [config] Added TryFromEnvValue & Merge support for
tracing::Level
. - [config] Removed #[env::test] due to a buggy interface.
Full Changelog: 0.1.2...0.1.3
v0.1.2
- Upgrade toolchain to Rust 1.86
- azalia: Add support for new trait upcasting in 1.86 (only avaliable if current compiler is Rust 1.86) (@auguwu)
- azalia-config: Update
sentry-types
to v0.37.0 (@renovate-bot, #226) - azalia-remi: Update
aws-sdk-s3
to v1.82.0 (@renovate-bot, #225)
Full Changelog: 0.1.1...0.1.2
v0.1.1
Additions
- [config] Add
sentry
feature for parsing DSNs in Rust
Fixes
- [config] Remove the restriction of
TryParseError
(andMapTryParseError
)'s generics to beTryFromEnvValue
to be any generic. In cases likePathBuf
returning this error:
error[E0277]: `?` couldn't convert the error: `std::path::PathBuf: std::fmt::Display` is not satisfied
--> /git/charted/server/crates/configuration/src/server/ssl.rs:54:39
|
54 | cert: env::try_parse(CERT)?,
| --------------------^ `std::path::PathBuf` cannot be formatted with the default formatter; call `.display()` on it
| |
| this can't be annotated with `?` because it has type `Result<_, azalia::azalia_config::env::TryParseError<std::path::PathBuf>>`
|
= help: the trait `std::fmt::Display` is not implemented for `std::path::PathBuf`
= note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
= note: required for `azalia::azalia_config::env::TryParseError<std::path::PathBuf>` to implement `std::error::Error`
= note: required for `eyre::Report` to implement `std::convert::From<azalia::azalia_config::env::TryParseError<std::path::PathBuf>>`
Full Changelog: 0.1.0...0.1.1