We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Discussed in yesterday's SIG, we should start opening issues to track when we do not support latest (stable) releases of an instrumented library.
We should label these, e.g. test latest deps(?)
test latest deps
Will close this issue once existing instrumentations have been reviewed and issues have been opened as needed.
The text was updated successfully, but these errors were encountered:
Closing, I think documenting on supported-libraries.md is good enough tracking, and this will be "enforced" by #12945
Sorry, something went wrong.
No branches or pull requests
Discussed in yesterday's SIG, we should start opening issues to track when we do not support latest (stable) releases of an instrumented library.
We should label these, e.g.
test latest deps
(?)Will close this issue once existing instrumentations have been reviewed and issues have been opened as needed.
The text was updated successfully, but these errors were encountered: