Release v0.3.0 against new branch
#1133
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
This updates the info for the full release as well as includes a missed breaking change.
JesseAbram
approved these changes
Oct 23, 2024
HCastano
added a commit
that referenced
this pull request
Nov 8, 2024
* Bump version from to `v0.3.0` * Update `CHANGELOG` This updates the info for the full release as well as includes a missed breaking change. * Use released version of `tdx-quote` * Get rid of warning when building tests * Update `Unreleased` section link
HCastano
added a commit
that referenced
this pull request
Nov 11, 2024
* Release `v0.3.0` against new branch (#1133) * Bump version from to `v0.3.0` * Update `CHANGELOG` This updates the info for the full release as well as includes a missed breaking change. * Use released version of `tdx-quote` * Get rid of warning when building tests * Update `Unreleased` section link * TaploFmt
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.
In #1129 I made a new base branch for the release called
release/v0.3.0. This caused a problem since that's the naming convention we used for tags, creating an ambiguous situation for Git. What I should've done was named the branchrelease-v0.3.0(note the dash instead of the backslash).While I could push forward and have a tag and branch with the same name I figured it would be better to address this by making a new PR targeting a non-conflicting base branch. I'm gonna have to delete the base branch for #1129 eventually, so note that the diff there might look a little wonky.
There are no code differences between this and #1129.