-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Update .NET logging framework compatability info #15527
Conversation
the table was incomplete and missing details, I re-organized it and updated it
also replaced known compatible versions because we will never be able to keep that list up to date. Replaced it with minimum agent version which is important for customers
Hi @brnhensley 👋 Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days. Gatsby Cloud will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 20 to 30 minutes). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, we can publish once the verify-mdx failure resolves itself!
✅ docs-website-develop deploy preview ready
|
Publishing with failed verify-mdx as the only gating error is the |
Updated the individual compatibility docs for Core and Framework. I replaced the known compatible versions with minimum versions and agent versions. Known compatible version lists are really tough to keep up to date and I'm not sure they are as valuable as a list of minimums or versions with known issues.
I also replaced the confusing bullet point list of compatibility info in the LIC doc with a table that is easier to read.
Please follow conventional commit standards
in your commit messages and pull request title.
Give us some context
links to related docs, screenshots, etc.