Hey there,

we have this cascade of deps where merge uses an unmaintained 
`proc-macro-error` crate.

Would you be able to migrate it and push a new release or would you mind 
us (rustic-rs org) taking over maintenance of the `merge-rs` crate in 
our org?

We use it quite a lot and it would be nice to keep it updated. You can 
add me to `merge`, `merge-derive` and `merge-derive-hashmap` via the 
crates.io dashboard owner invites.

Cheers,

Simon

Our advisory:

proc-macro-error 1.0.4 
registry+https://github.com/rust-lang/crates.io-index │ 
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 
unmaintained advisory detected │ ├ ID: RUSTSEC-2024-0370 ├ Advisory: 
https://rustsec.org/advisories/RUSTSEC-2024-0370 ├ proc-macro-error's 
maintainer seems to be unreachable, with no commits for 2 years, no 
releases pushed for 4 years, and no activity on the GitLab repo or rLab 
repo or response to email. proc-macro-error also depends on `syn 1.x`, 
which may be bringing duplicate dependencies into dependant build trees. 
## Possible Alternative(s) - [manyhow](https://crates.io/crates/manyhow) 
- [proc-macro-error2](https://crates.io/crates/proc-macro-error2) - 
[proc-macro2-diagnostics](https://github.com/SergioBenitez/proc-macro2-diagnostics)oc-macro2-diagnostics) 
├ Announcement: 
https://gitlab.com/CreepySkeleton/proc-macro-error/-/issues/20 ├ 
Solution: No safe upgrade is available! ├ proc-macro-error v1.0.4 └── 
merge_derive v0.1.0 └── merge v0.1.0 ├── rustic-rs v0.8.1 ├── 
rustic_backend v0.3.0 │ └── rustic-rs v0.8.1 (*) └── rustic_core v0.4.0 
├── rustic-rs v0.8.1 (*) ├── rustic_backend v0.3.0 (*) └── 
rustic_testing v0.2.1 └── (dev) rustic-rs v0.8.1 (*)