Skip to content

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Oct 23, 2024

Backport of #6434 to release/9.0

/cc @sebastienros

Customer Impact

Testing

Risk

Regression?

Microsoft Reviewers: Open in CodeFlow

@eerhardt
Copy link
Member

<!-- In preview until the public API is validated. -->
<SuppressFinalPackageVersion>true</SuppressFinalPackageVersion>

This needs to be removed.

@joperezr
Copy link
Member

/azp run dotnet.aspire

Copy link

Azure Pipelines successfully started running 1 pipeline(s).


using System.Diagnostics.CodeAnalysis;

[assembly: Experimental("ASPIREHOSTINGPYTHON001", UrlFormat = "https://aka.ms/dotnet/aspire/diagnostics#{0}")]
Copy link
Member

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?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

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)

Copy link
Member

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.

@joperezr
Copy link
Member

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.

Copy link
Member

@eerhardt eerhardt left a 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}")]
Copy link
Member

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.

@joperezr joperezr merged commit eeb0e7c into release/9.0 Oct 25, 2024
9 checks passed
@joperezr joperezr deleted the backport/pr-6434-to-release/9.0 branch October 25, 2024 22:20
joperezr added a commit to joperezr/aspire that referenced this pull request Nov 13, 2024
…/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
@github-actions github-actions bot locked and limited conversation to collaborators Nov 25, 2024
@github-actions github-actions bot added the area-integrations Issues pertaining to Aspire Integrations packages label Mar 10, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-integrations Issues pertaining to Aspire Integrations packages

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants