Soften warning about bugs and maintenance in README#117
Merged
Aurumaker72 merged 2 commits intomainfrom Jan 12, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR softens the severity of the README warning from CAUTION to WARNING and significantly reduces its content. The change is motivated by the upcoming 0.8.0 release which will resolve the critical jitter issue mentioned in the original warning.
Changes:
- Downgraded warning level from CAUTION to WARNING
- Removed maintenance status details and simplified the message to focus on recommending version 0.6.0
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Pull Request Test Coverage Report for Build 20926960456Details
💛 - Coveralls |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
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
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.
The coming 0.8.0 version won't have the critical jitter issue, so it's probably worth toning this warning down a notch.
While the maintenance warning is still somewhat fitting, I don't see the current state of affairs being critical enough to warrant that visible spot in the readme.