0.6.0 release - #248
Merged
Merged
Conversation
anirudhrb
requested review from
NunoDasNeves,
liuw,
praveen-pk and
russell-islam
as code owners
August 13, 2025 18:15
anirudhrb
force-pushed
the
release-0.5.3
branch
from
August 13, 2025 18:18
7ae0830 to
af178c5
Compare
Collaborator
Author
|
Should this release be 0.6.0 since new (backwards compatible) functionality was added? |
Update Cargo.toml and CHANGELOG for 0.6.0 release Signed-off-by: Anirudh Rayabharam <anrayabh@microsoft.com>
anirudhrb
force-pushed
the
release-0.5.3
branch
from
August 13, 2025 18:47
af178c5 to
59b766f
Compare
anirudhrb
changed the title
Collaborator
Yes, if the new API added or changed. Looks good to me. |
russell-islam
approved these changes
Aug 13, 2025
NunoDasNeves
approved these changes
Aug 13, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary of the PR
Prepare for release by bumping up the version and updating changelog.
Requirements
Before submitting your PR, please make sure you addressed the following
requirements:
git commit -s), and the commit message has max 60 characters for thesummary and max 75 characters for each description line.
test.
Release" section of CHANGELOG.md (if no such section exists, please create one).
unsafecode is properly documented.