[Not for merging] netcoreapp3.1 for Prometheus middleware project #3559
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.
No need for merging or making a decision at the moment. Opening this PR just to illustrate things, but I plan to close it and just open an issue.
This needs to be an additional discussion point as we consider how to handle #3448.
The Prometheus ASP.NET Core middleware project previously targeted
netcoreapp3.1
. Upon merging our net7.0 branch, it now just targetsnet6.0
.Do we only want to support net6.0+ with our Prometheus exporter?
Another option may be to "support" it in the way this PR proposes by suppressing the build warnings for the purposes of our build, though I believe this would still result in end users getting the warnings.
Maybe we'd take the stance that we don't really support the netcoreapp3.1 version even though we offer a version that targets it?