Built: Update revapi to 1.4.1 #8906
Closed
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
I don't think this is necessary since the API doesn't change between minor versions, but it is part of the release process :)
|
FYI, related to |
jbonofre
approved these changes
Oct 23, 2023
|
I believe we typically don't update RevAPI to patch versions (at least we haven't done so for 1.2.1 or 1.3.1 in the past) |
It is because revAPI expects a tag from the main branch. For point release, the tags are not created from the main branch. Hence, revAPI doesn't work. |
|
@ajantha-bhat thanks for the context, closing this one |
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.
I don't think this is necessary since the API doesn't change between minor versions, but it is part of the release process :)