We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
As discussed on Gitter, it seems reasonable to relax the .NET Core SDK version pinning a bit. Right now, this repo is tightly pinned to 3.1.102.
3.1.102
See here for configuration options in global.json.
global.json
Pinning to the feature band (e.g. 3.1.1xx) seems to give the right trade off between build consistency and developer friendliness.
3.1.1xx
The text was updated successfully, but these errors were encountered:
Pin .NET Core SDK version to latest feature band
b1ae127
Pin the .NET Core SDK version to the `3.1.1xx` feature band. Do not allow prerelease versions. Fixes serilog#175
Successfully merging a pull request may close this issue.
As discussed on Gitter, it seems reasonable to relax the .NET Core SDK version pinning a bit. Right now, this repo is tightly pinned to
3.1.102
.See here for configuration options in
global.json
.Pinning to the feature band (e.g.
3.1.1xx
) seems to give the right trade off between build consistency and developer friendliness.The text was updated successfully, but these errors were encountered: