prepare release v1.13.9 #3996
Merged
prepare release v1.13.9 #3996
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
nkysg
requested review from
jolestar,
yourmoonlight,
sanlee42 and
LemonHX
as code owners
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #3996 +/- ##
==========================================
- Coverage 54.71% 54.62% -0.08%
==========================================
Files 640 640
Lines 70111 70111
==========================================
- Hits 38351 38288 -63
- Misses 31760 31823 +63
Flags with carried forward coverage won't be shown. Click here to find out more. see 10 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
sanlee42
approved these changes
Dec 19, 2023
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.
Pull request type
prepare release v1.13.9
Please check the type of change your PR introduces:
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Other information