-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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 version to 9.0-alpha1 #90558
Conversation
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue Details🎉
|
@dotnet/ncl or @ViktorHofer do you know how to address the Quic failure message about opting into preview features?:
|
Strange, HTTP already has the preview feature set:
Perhaps something in the SDK? BTW This may also break the Enterprise pipeline - at least it always did in the past. |
EnablePreviewFeatures has an interesting behavior that it only works on the most current TFM. Looks like we might need some other solution here. |
removing |
Maybe manually including the attribute in the .NET 8 build (instead of using the SDK property) would work. |
/azp-run runtime-libraries stress-http |
/azp-run runtime-libraries enterprise-linux |
@carlossanlop @wfurt I looked more into the failure. Here's whats happening:
There are two possible solutions:
@carlossanlop which would you rather do? I'd prefer the second option personally. |
I've started down the path of the second option locally. I'll try to finish it up tomorrow so I can push it out (just fixing up APICompat baselining). |
…void regressions in .NET 8.0 targets and clean up .NET 8->.NET 9 API compat baselining.
…n the 9.0 variants of the packages.
I agree. This PR only has the changes required for the rebranding, not the TFM upgrade. |
…convert Version=8.0.0.0 to Version=9.0.0.0)
@@ -139,6 +139,48 @@ | |||
<Left>ref/net8.0/System.Linq.Expressions.dll</Left> | |||
<Right>lib/net8.0/System.Linq.Expressions.dll</Right> | |||
</Suppression> | |||
<Suppression> |
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.
These changes should be reverted. Same for the test binary file below.
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.
The build fails without these two changes.
* Adding PACKAGE.md to System.Runtime.Caching package * add Remarks * move PACKAGE.md to src folder * update per PR feedback * add important block
New sdk error on windows:
The log doesn't show the exit code. I'll check locally. |
I'm not sure what is wrong here. The Update: the warning is emitted if the powershell version is |
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.
The AssemblyVersion property in Versions.props must be hardcoded to 8.0.0.0 for now. We had the same issue last release and noticed that updating the TFM must happen in conjunction with reving the major assembly version.
Please also undo the changes in both CompatibilitySuppressions.xml, the TestData.resources one and the PACKAGE.md change which looks unrelated.
Prompted by the following getting caught as a warning, and converted to an error: ``` EXEC : error : dotnet-install: Failed to check the disk space. Installation will continue, but it may fail if you do not have [D:\a\_work\1\s\src\mono\wasm\Wasm.Build.Tests\Wasm.Build.Tests.csproj] enough disk space. dotnet-install: Extracting the archive. ```
This was missing for the windows case! |
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
@radical if the WASM MT failures are known, can you merge this in? |
🎉