Bump version to 0.4.1 #708
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Prepare a release of `topiary-queries` with the latest Nickel queries. For the time being, it was decided that it's ok to bump the minor version for such an update.
yannham
force-pushed
the
chore/0.4.1-update
branch
from
40fc460 to
dded060
Compare
Xophmeister
approved these changes
Jun 5, 2024
|
Let's get a stamp of approval from @ErinvanderVeen as well, to be sure it's a consensus |
ErinvanderVeen
approved these changes
Jun 6, 2024
|
This is good for now. I think in the future we want to decouple the versions if possible. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prepare a release of
topiary-querieswith 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.0on GitHub and crates.io until the next update, and just publishtopiary-queries. But I'm happy to do otherwise.Checklist
Checklist before merging: