docs: add versioning guide #3462
Merged
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
|
size-limit report 📦
|
lesliecdubs
reviewed
Jun 29, 2023
contributor-docs/versioning.md
Outdated
|
|
||
| semver bump: **minor** | ||
|
|
||
| When a type is broadeded, it is now possible for that type to include both the |
broccolinisoup
approved these changes
Jun 30, 2023
Comment on lines
+48
to
+49
| | | [The type of a prop is broadened](#the-type-of-a-prop-is-broadened) | `minor` | | ||
| | | [The type of a prop is narrowed](#the-type-of-a-prop-is-narrowed) | `major` | |
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 is a follow-up to: #2753 with a narrowed scope of changes that I believe we have consensus on with respect to semver 👀 Figured it'd be useful to get this document into
contributor-docsand add to it over time as we run into things in our release process.Would love to know what you all think of this format and if there is anything that should be added, edited, or if there is a better approach to documenting these kinds of conventions so that we can refer to them in reviews and in our release process.