Prepare a release of topiary-queries with the latest Nickel queries to crates.io. For the time being, it was decided that it's ok to bump the patch version for such an update. I hesitated to do this just for topiary-queries, but that would mean to stop using the workspace version for topiary-queries, but the added risk of being out of sync (or to just forget to bump topiary-queries's version during an update) isn't worth it IMHO. Instead, I think we should just accept to bump the whole workspace version.
I don't know if a GitHub release is very useful to do in this case (or a cargo release of other Topiary crates). I think it's fine to keep all the others crates at 0.4.0 on GitHub and crates.io until the next update, and just publish topiary-queries. But I'm happy to do otherwise.
Prepare a release of
topiary-queries
with the latest Nickel queries tocrates.io
. For the time being, it was decided that it's ok to bump the patch version for such an update. I hesitated to do this just fortopiary-queries
, but that would mean to stop using the workspace version fortopiary-queries
, but the added risk of being out of sync (or to just forget to bumptopiary-queries
's version during an update) isn't worth it IMHO. Instead, I think we should just accept to bump the whole workspace version.I don't know if a GitHub release is very useful to do in this case (or a cargo release of other Topiary crates). I think it's fine to keep all the others crates at
0.4.0
on GitHub and crates.io until the next update, and just publishtopiary-queries
. But I'm happy to do otherwise.Checklist
Checklist before merging: