-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(*): write to stderr for errors and warnings #611
Conversation
Co-authored-by: Artem Derevnjuk <[email protected]>
@maksadbek you should describe the breaking changes as follows: After the merge, a new major version (v13) will be released. |
@adirdidi @bararchy FYI, the logging fix will trigger v13 release - breaking change. |
@orubin not immediately ofc, we will release the v13 release candidate (i.e., v13.0.0-next.1) first. We can postpone the final release of v13 and maintain both v12.x and the v13.x.x-next.x for a while and you can plan other breaking changes and migration util this moment. @maksadbek in that case, you need to keep working in |
Will update you about v13 release, we may add one more feature to it (discovery). |
BREAKING CHANGE: Warning logs are now written to stderr instead of stdout. Supersedes: #611 Co-authored-by: Maksadbek <[email protected]>
BREAKING CHANGE: Warning logs are now written to
stderr
instead ofstdout
.