Skip to content

Conversation

@joperezr
Copy link
Member

@joperezr joperezr commented Oct 19, 2024

These changes will enable signing in our builds, as well as marking the packages as stable. Some packages will not be able to be marked stable yet as we need to flow some dependencies yet, so those will be marked as unstable for now.

Microsoft Reviewers: Open in CodeFlow

<VersionPrefix>$(MajorVersion).$(MinorVersion).$(PatchVersion)</VersionPrefix>
<PreReleaseVersionLabel Condition="'$(SuppressFinalPackageVersion)' != 'true'">rc.2</PreReleaseVersionLabel>
<PreReleaseVersionLabel Condition="'$(PreReleaseVersionLabel)' == ''">preview.5</PreReleaseVersionLabel>
<PreReleaseVersionLabel>preview.5</PreReleaseVersionLabel>
Copy link
Member Author

Choose a reason for hiding this comment

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

We no longer need the distinction as packages will be stable or preview 5 depending or not if their stable version is being suppressed

</ItemGroup>
</Target>

<Target Name="ValidatePreReleaseLabelIsCorrectForPreviewPackages"
Copy link
Member Author

Choose a reason for hiding this comment

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

We no longer need this target as we are no longer producing different prerelease labels.

<EnablePackageValidation Condition="'$(EnablePackageValidation)' == ''">true</EnablePackageValidation>
<PackageValidationBaselineVersion Condition="'$(EnablePackageValidation)' == 'true' and '$(PackageValidationBaselineVersion)' == ''">$(BaselineVersionForPackageValidation)</PackageValidationBaselineVersion>
<!-- For Aspire.Hosting.Azure* packages, we need to ingest the new Azure.Provisioning stable packages in order for us to produce stable bits. -->
<SuppressFinalPackageVersion Condition="$(MSBuildProjectName.StartsWith('Aspire.Hosting.Azure'))">true</SuppressFinalPackageVersion>
Copy link
Member Author

Choose a reason for hiding this comment

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

This is temporary and will get removed once we ingest the stable version of Azure.Provisioning. cc: @eerhardt @davidfowl

<Description>A PostgreSQL® provider for Entity Framework Core that integrates with Aspire, including connection pooling, health checks, logging, and telemetry.</Description>
<PackageIconFullPath>$(SharedDir)PostgreSQL_logo.3colors.540x557.png</PackageIconFullPath>
<!-- We need to ingest the stable version of EF and npgsql in order for us to produce stable bits. -->
<SuppressFinalPackageVersion>true</SuppressFinalPackageVersion>
Copy link
Member Author

Choose a reason for hiding this comment

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

FYI: @eerhardt will need to figure out what to do about this one given the npgsql dependency.

@joperezr
Copy link
Member Author

Merging in favor of getting a release/9.0 build to test. Will address any follow up questions in a follow up PR.

@joperezr joperezr merged commit a6520f7 into dotnet:release/9.0 Oct 21, 2024
9 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Nov 21, 2024
@github-actions github-actions bot added the area-integrations Issues pertaining to Aspire Integrations packages label Mar 10, 2025
@joperezr joperezr deleted the EnableSigningAndStabilize branch April 1, 2025 17:43
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.

1 participant