Michael Uti

I seem to be having this same issue. I found [rust-crypto](https://github.com/DaGenix/rust-crypto) to be the culprit. [It has also been adviced not to use it](https://rustsec.org/advisories/RUSTSEC-2016-0005.html).

No, [we still limit concurrency](https://github.com/build-trust/ockam/blob/f2e399804652c8afe0ffaa82feedb94ebde743a0/tools/nextest/.config/nextest.toml#L7) when running the examples, we will need to revisit the example code.

I am closing this issue in favour of https://github.com/build-trust/ockam/issues/3619 and https://github.com/build-trust/ockam/issues/3005

~I don't think this is needed as we now use `cargo-readme` to generate readme files cc @etorreborre @mrinalwadhwa~

I updated the issue to use cargo-readme instead to update readme files

Closing now. Thanks everyone

> suggested schedule We will be running this check for every PR that is to be merged, this will ensure that contributors themselves update the Notice file if it's outdated,...

Notice CI still fails https://github.com/build-trust/ockam/actions/runs/8923006071/job/24507630076?pr=7872 I think we are missing something

> > Notice CI still fails https://github.com/build-trust/ockam/actions/runs/8923006071/job/24507630076?pr=7872 I think we are missing something > > @metaclips Could you please clarify if the workflow is checking out the most current version...

> > Seems we were using an outdated version of cargo-deny locally. I was able to push an updated version of the Notice file and CI now passes. > >...