Create a checklist of things to verify when new crates are introduced.

[thomcc]

Two things that were missed in the ockam_transport_ble review that we should be sure not to miss for new crates (for example ockam_transport_smoltcp in #2213):

1. No CHANGELOG.md file. Initially, it should be empty. It's possible this should instead be handled by the changelog generation script.
2. Use of a path = ... and no version = ... for the dependency on ockam (chore(rust): fixup ockam_transport_ble for publish (missing crate version) #2525). This failure manifests quite late in the process, and not during a part that handles interruption well so it's pretty important we catch this one in the future.

More broadly, there are certainly other things to check as well. We should make a list of these somewhere. It probably is too rare that we add new crates to be worth automating, but perhaps that's worthwhile too.

---

We love helping new contributors! ❤️
If you have questions or need help as you explore, please join us on Discord. If you're looking for other issues to contribute to, please checkout our good first issues.

[PsychoPunkSage]

Hi @thomcc
Can I work on this issue. it seems no one is working on it. Can I have a look at this issue?

[metaclips]

@PsychoPunkSage it’s all yours

[PsychoPunkSage]

Hi @metaclips
I made a PR. Please have a look at it.
Thank You