-
Notifications
You must be signed in to change notification settings - Fork 701
[release/9.0] Mark Aspire.Hosting.Python as experimental #6460
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
Conversation
aspire/src/Aspire.Hosting.Python/Aspire.Hosting.Python.csproj Lines 9 to 10 in b1549df
This needs to be removed. |
/azp run dotnet.aspire |
Azure Pipelines successfully started running 1 pipeline(s). |
|
||
using System.Diagnostics.CodeAnalysis; | ||
|
||
[assembly: Experimental("ASPIREHOSTINGPYTHON001", UrlFormat = "https://aka.ms/dotnet/aspire/diagnostics#{0}")] |
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.
Just to make sure, is the intention really to mark ALL APIs as experimental as opposed to just the new ones? Presumably we would want to keep the other ones not as experimental and instead just obsolete them?
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.
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.
From what I am seeing in the PublicAPI files, all previous have been obsoleted, so everything is new. And everything is
- one resource (PythonAppResource)
- two extension methods (AddPythonApp)
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.
Yes, I think we just make ALL APIs in this library Experimental for 9.0. All the previous APIs are obsolete. And all the new APIs are experimental.
We need to take this change for Aspire.Hosting.Python, so this does meet the bar and is approved. Let's just make sure we get confirmation on the question I asked above. |
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
|
||
using System.Diagnostics.CodeAnalysis; | ||
|
||
[assembly: Experimental("ASPIREHOSTINGPYTHON001", UrlFormat = "https://aka.ms/dotnet/aspire/diagnostics#{0}")] |
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.
Yes, I think we just make ALL APIs in this library Experimental for 9.0. All the previous APIs are obsolete. And all the new APIs are experimental.
…/9.0 #### AI description (iteration 1) #### PR Classification Code cleanup and dependency updates. #### PR Summary This pull request merges changes from `release/9.0` into `internal/release/9.0`, addressing several work items related to security, dependency updates, and code cleanup. - Removed `MilvusClient` creation logic and health checks from `src/Aspire.Hosting.Milvus/MilvusBuilderExtensions.cs`. - Updated various package dependencies in `Directory.Packages.props` and `eng/Version.Details.xml`. - Added `AssemblyInfo.cs` to `src/Aspire.Hosting.Python` to mark it as experimental. - Updated container image tags in `src/Aspire.Hosting.Milvus`, `src/Aspire.Hosting.MySql`, `src/Aspire.Hosting.Elasticsearch`, and `src/Aspire.Hosting.Keycloak`. - Removed deprecated package references and suppressed final package version in `src/Aspire.Hosting.Milvus/Aspire.Hosting.Milvus.csproj`. Related work items: dotnet#5994, dotnet#6054, dotnet#6298, dotnet#6377, dotnet#6417, dotnet#6435, dotnet#6451, dotnet#6460, dotnet#6498
Backport of #6434 to release/9.0
/cc @sebastienros
Customer Impact
Testing
Risk
Regression?
Microsoft Reviewers: Open in CodeFlow