Release a new version

[wackywendell]

There's been a suite of recent changes to substrait-validator, and it would be useful to release a new version, as mentioned briefly here.

I'm opening this issue to raise the question - what features or changes (outside the documented release chores) do we want before we're ready for a new version?

[mbrobbel]

In my opinion we can just bump versions and push a new release now and repeat this whenever beneficial.

[westonpace]

In my opinion we can just bump versions and push a new release now and repeat this whenever beneficial.

Agreed. Ideally we could automate the release steps in the future too so that we can have push-button releases.

[wackywendell]

Ah, ok! Fair enough.

🤔 I'm not sure how automated it currently is / how well it will work; it looks like there's a Github Action for releasing (Python too), so if we tag the commit with a version number that should trigger it? I guess we'll have to see how functional that is 🤞

I can put together a PR for that. @mbrobbel - did you want to get #276 in first? It looks like that would update the Python packager maturin, which might affect this.

[mbrobbel]

did you want to get #276 in first?

No, let's not block this release on that.

[wackywendell]

OK! I'll put together a PR for that. Any thoughts on the version number?

We're currently at 0.0.11; perhaps its time to go to 0.1.0? This seems like more than a patch update, but pre-1.0 I'm not sure it matters much...

[wackywendell]

^ OK! I made a PR. I went with 0.1.0 for now, but its real easy to switch if there are other opinions. Thanks for your help on this!