Ivan Leshchenko

Hi! At the moment, to compose different custom verification methods/signature suites into structures similar to those provided by `Any*`, a developer has to manually re-implement at least the `crypto_suites!` macro,...

- Bumps some dependencies workspace-wide (this should reduce the dependency tree in general, since new projects usually use the latest library versions) - Removes the `rustls` support by default, allowing...

### I have found these related issues/pull requests #3195 seems to mention this issue, but in a different context. ### Description This codegen snippet omits generic types when generating the...

## Description Per [Section 4.1](https://www.ietf.org/archive/id/draft-ietf-oauth-selective-disclosure-jwt-22.html#section-4.1) of the SD-JWT specification, `_sd_alg` field is optional and in its absence implementations [should assume](https://www.ietf.org/archive/id/draft-ietf-oauth-selective-disclosure-jwt-22.html#name-hash-function-claim) the default value of `sha-256`. ## Tested `cargo check`

Closes #1466

contour: add module

3

### Description Add [Contour terminal](https://github.com/contour-terminal/contour) module. ### Checklist - [x] Change is backwards compatible. - [x] Code formatted with `./format`. - [x] Code tested through `nix-shell --pure tests -A run.all`....

Expose `http::Uri` to layers passed to `ClientBuilder::connector_layer`

1

Hi. I'm currently trying to create a layer that performs some actions depending on the request URL. As the HTTP client itself is passed to different application components, I find...