Update serde to 1.x.y

[korczis]

I am opening this PR to open discussion about plans to migrate to serde 1.x.y

[GitCop]

There were the following issues with your Pull Request

• Commit: f15c2fc

• Commits must be in the following format: %{type}(%{scope}): %{description}

• Commit: 7f30540

• Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/rustless/valico/blob/master/CONTRIBUTING.md

---

This message was auto-generated by https://gitcop.com

[emk]

@korczis I could also use a version of valico that worked with stable serde.

[emk]

@korczis @camjackson @s-panferov

Hello! I'm the principal author of compose_yml and cage, two Docker-related development tools that rely on valico. We've been very happy with valico for schema validation!

Recently, I updated both tools to use serde 1.0. Unfortunately, this meant that I had to disable valico, which caused a couple of fairly major regressions in compose_yml and cage. I would love to get back valico's great validation support.

Is there anything I could do to help get this PR merged (and the corresponding changes to jsonway at korczis/jsonway@8a142a0)? I'd be happy to devote some engineering time to this.

Also, this would have the advantage of leaving valico in a stable state for the long term, because serde 1.0 is likely to stick around indefinitely. Also, it would be possible to re-export serde_json as valico::serde_json, which would allow valico to keep working even if serde 2.0 is released some day.

Thank you very much for valico, and for considering this PR! Please let me know if there's anything at all that I can to smooth the merging process.

[JordiPolo]

Really interested on this also, @korczis any progress?