docs: Bump the next version to 2.0.0 in more docs files #1787
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
Because the fixes to date range searches do change existing behaviour, even though they are definite improvements.
claremacrae
added
the
scope: documentation
6 tasks
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.
Description
Because the fixes to date range searches do change existing behaviour, even though they are definite improvements.
This is the second half of #1785. I accidentally missed out some files in that.
Motivation and Context
Because the fixes to date range searches do change existing behaviour, even though they are definite improvements.
How has this been tested?
Viewing docs locally.
Screenshots (if appropriate)
Types of changes
Changes visible to users:
docs- improvements to any documentation content for users)Checklist
yarn run lint.Terms