-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Bump main branding to 8.0 #73985
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
Bump main branding to 8.0 #73985
Conversation
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsDo not merge. This depends on snapping first. This PR is loosely based on what we did last year: https://github.com/dotnet/runtime/pull/57095/files I suspect this change is incomplete, since many of the elements modified in last year's PR do not exist today.
|
eng/Versions.props
Outdated
| <!-- Set assembly version to align with major and minor version, | ||
| as for the patches and revisions should be manually updated per assembly if it is serviced. --> | ||
| <AssemblyVersion>$(MajorVersion).$(MinorVersion).0.0</AssemblyVersion> | ||
| <AssemblyVersion>$(PreviousReleaseMajorVersion).$(MinorVersion).0.0</AssemblyVersion> |
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.
| <AssemblyVersion>$(PreviousReleaseMajorVersion).$(MinorVersion).0.0</AssemblyVersion> | |
| <AssemblyVersion>7.$(MinorVersion).0.0</AssemblyVersion> |
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.
I'll apply your suggestion, but can you please explain why this value can't stay in $(MajorVersion)? Why do we need to use 7 instead of 8?
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.
In the past release when we branded main to .NET 7 we didn't bump the assembly versions as part of the branding update. We only incremented the package major version to avoid bin clashes when packages being uploaded to the same feed.
Incrementing the assembly versions should happen afterwards to not block this PR: I assume that the assembly update could cause other issues that would need to be resolved.
Co-authored-by: Viktor Hofer <[email protected]>
|
@ViktorHofer any chance you can give a quick look at last year's PR and let me know if I missed anything? https://github.com/dotnet/runtime/pull/57095/files |
ViktorHofer
left a comment
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.
LGTM. Unsure if the SdkBandVersion needs to be incremented as well, but that can probably be done in a follow-up.
|
Ci failures unrelated. |
Do not merge. This depends on snapping first.
This PR is loosely based on what we did last year: https://github.com/dotnet/runtime/pull/57095/files
I suspect this change is incomplete, since many of the elements modified in last year's PR do not exist today.