Update Changelog and Version to '0.3.2' #703
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
InsertCreativityHere
requested review from
pepone,
externl and
bernardnormier
bernardnormier
approved these changes
Sep 10, 2024
pepone
approved these changes
Sep 10, 2024
externl
approved these changes
Sep 11, 2024
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.
This PR adds the necessary changelog entries, and updates the version of
slicecto0.3.2.I went back and forth between
0.3.2and0.4.0, and settled on0.3.2because I think this is what semver would dictate.There is very little difference between this release and the last. Only 2 minor bug fixes, and support for file hashing, a pretty minor feature only used by our tooling, and even then, only for it's telemetry.
We always knew that eventually the versions for
icerpc-csharpandslicecwould diverge.But, if you think we should keep the versions in sync for a little longer, feel free to say so.
I'm not married to the version, it's just what I thought felt most correct.