Update stability info in documentation #3216
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
|
Could you update the docs? They have this paragraph too. |
Good call, updated several places in the docs. |
|
How about also updating this line? |
Done! |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3216 +/- ##
===============================================
Coverage 100.00000% 100.00000%
===============================================
Files 124 124
Lines 18770 18770
Branches 1269 1269
===============================================
Hits 18770 18770
🚀 New features to boost your workflow:
|
agronholm
reviewed
Feb 26, 2025
agronholm
reviewed
Feb 26, 2025
jakkdl
reviewed
Feb 27, 2025
Zac-HD
approved these changes
Feb 27, 2025
graingert
approved these changes
Feb 28, 2025
|
lgtm |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 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.
This PR updates the README to better reflect Trio’s current maturity. The previous wording hadn’t been updated since it was originally written eight years ago and no longer accurately represented Trio’s suitability for production use.
No functional changes—just a documentation update for clarity.