Update to latest Configuration Binder source generator #1616
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Now that 8.0.1 has shipped, we can remove the workarounds added in dotnet#535.
dotnet-issue-labeler
bot
added
the
area-integrations
eerhardt
commented
Jan 10, 2024
| <MicrosoftExtensionsDependencyInjectionAbstractionsPackageVersion>8.0.0</MicrosoftExtensionsDependencyInjectionAbstractionsPackageVersion> | ||
| <MicrosoftExtensionsHostingAbstractionsPackageVersion>8.0.0</MicrosoftExtensionsHostingAbstractionsPackageVersion> | ||
| <MicrosoftExtensionsHostingPackageVersion>8.0.0</MicrosoftExtensionsHostingPackageVersion> | ||
| <MicrosoftExtensionsHttpPackageVersion>8.0.0</MicrosoftExtensionsHttpPackageVersion> | ||
| <MicrosoftExtensionsLoggingAbstractionsPackageVersion>8.0.0</MicrosoftExtensionsLoggingAbstractionsPackageVersion> | ||
| <MicrosoftExtensionsOptionsPackageVersion>8.0.0</MicrosoftExtensionsOptionsPackageVersion> | ||
| <MicrosoftExtensionsOptionsPackageVersion>8.0.1</MicrosoftExtensionsOptionsPackageVersion> | ||
| <MicrosoftExtensionsPrimitivesPackageVersion>8.0.0</MicrosoftExtensionsPrimitivesPackageVersion> | ||
| <MicrosoftAspNetCoreOpenApiPackageVersion>8.0.0</MicrosoftAspNetCoreOpenApiPackageVersion> |
There was a problem hiding this comment.
Note that all the libraries from dotnet/aspnetcore now have a 8.0.1 version because they ship every month, whether there are changes or not. I didn't update here because I don't think we should unless there is a blocking bug we need.
Thoughts?
There was a problem hiding this comment.
Can we introduce $(AspNetVersion) ?
There was a problem hiding this comment.
Let's say we did and we wanted to consume a new patch version Microsoft.AspNetCore.OpenApi, would it make sense for all the packages to go to 8.0.1 just because we needed a new version of OpenApi?
sebastienros
approved these changes
Jan 11, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Now that 8.0.1 has shipped, we can remove the workarounds added in #535.
Microsoft Reviewers: Open in CodeFlow