Prepare for release 0.0.2

[bfish713]

Description

Preparing a release for Seahorse to pin to. This just updates the cargo.toml to match what I plan to tag as the release.

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Linked to GitHub issue with discussion and accepted design OR have an explanation in the PR that describes this work.
• Wrote unit tests - N/A
• Updated relevant documentation in the code - N/A
• Added a relevant changelog entry to the Pending section in CHANGELOG.md - N/A
• Re-reviewed Files changed in the GitHub PR explorer

[alxiong]

Wait, why aren't we tagging 0.1.1? @bfish713

[bfish713]

Wait, why aren't we tagging 0.1.1? @bfish713

Oh it's a bit confusing, 0.1.1 will be the next version for jellyfish. We have to use 0.1.0 here because this PR EspressoSystems/jellyfish#57 seems have some breaking changes. So I can't use the most recent version of jellyfish. Let me know if that doesn't sound right

[alxiong]

We have to use 0.1.0 here because this PR EspressoSystems/jellyfish#57 seems have some breaking changes. So I can't use the most recent version of jellyfish.

I think issue 57 was mostly internal API changes, shouldn't affect downstream (at least not too much)? so did you try to use 0.1.1 and run into a lot of compiler err?

---

in any case, I think it's fine to use 0.1.0 for now. feel free to merge it.

[bfish713]

We have to use 0.1.0 here because this PR EspressoSystems/jellyfish#57 seems have some breaking changes. So I can't use the most recent version of jellyfish.

I think issue 57 was mostly internal API changes, shouldn't affect downstream (at least not too much)? so did you try to use 0.1.1 and run into a lot of compiler err?

in any case, I think it's fine to use 0.1.0 for now. feel free to merge it.

Yeah was having issues compiling using 0.1.1