v0.21.0 #2146
Merged
v0.21.0 #2146
Conversation
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
|
@christopherdro per your note here. |
Merged
pinpong
pushed a commit
to pinpong/react-native-maps
that referenced
this pull request
Feb 28, 2025
* Bump version to 0.21.0 * v0.21.0 * v0.21.0 * v0.21.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Does any other open PR do the same thing?
Nope!
What issue is this PR fixing?
Quite a few. Just packing up everything from the past 2 months for a new release!
How did you test this PR?
N/A
Following semantic versioning practices and based on the amount of time and number of changes between
masterandv0.20.1I opted to create a new minor version (0.21.0) than a new patch (0.20.2). However, it is my opinion that this would be an appropriate time to jump to the first major version (1.0.0) given the recent change in repository ownership and the maturity, size, and comprehensiveness of this library. It is typically appropriate to move from 0.X.X to 1.X.X once the public API is defined.I made these commits one file at a time, so whoever merges this should squash them into one.