-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
Use checked-in platform manifest in 3.1.2 #18250
Conversation
<IsTargetingPackBuilding Condition=" '$(DotNetBuildFromSource)' == 'true' ">false</IsTargetingPackBuilding> | ||
<IsTargetingPackBuilding | ||
Condition=" '$(IsTargetingPackBuilding)' == '' AND '$(VersionPrefix)' == '3.0.1' ">true</IsTargetingPackBuilding> | ||
Condition=" '$(IsTargetingPackBuilding)' == '' AND '$(VersionPrefix)' == '3.1.2' ">true</IsTargetingPackBuilding> |
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.
FYI I already made these changes in https://github.com/dotnet/aspnetcore/pull/18151/files so there may be some conflict when merging.
@@ -33,7 +33,7 @@ | |||
<!-- TargetingPackVersionPrefix is used by projects, like .deb and .rpm, which use slightly different version formats. --> | |||
<TargetingPackVersionPrefix>$(VersionPrefix)</TargetingPackVersionPrefix> | |||
<!-- Targeting packs do not produce patch versions in servicing builds. No API changes are allowed in patches. --> | |||
<TargetingPackVersionPrefix Condition="'$(IsServicingBuild)' == 'true'">$(AspNetCoreMajorVersion).$(AspNetCoreMinorVersion).0</TargetingPackVersionPrefix> | |||
<TargetingPackVersionPrefix Condition="'$(IsTargetingPackBuilding)' != 'true'">$(AspNetCoreMajorVersion).$(AspNetCoreMinorVersion).2</TargetingPackVersionPrefix> |
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.
👍 Good catch.
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.
This looks good to me based on the conversations I've had so far with @ericstj and @nguerrera
This was approved for 3.1.2 in #17957 |
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.
Looks good but please do a fake non-servicing build after cleaning your repo e.g. port to 'master'. That'll confirm build ordering doesn't mess up the changes to the App.Ref. (App.Runtime depends on App.Ref, not the other way 'round. But, I'm not sure about when the specific packaging targets run.)
@@ -53,7 +53,8 @@ This package is an internal implementation of the .NET Core SDK and is not meant | |||
<!-- Platform manifest and package override metatdata --> | |||
<ReferencePackSharedFxVersion>$(AspNetCoreMajorVersion).$(AspNetCoreMinorVersion).0</ReferencePackSharedFxVersion> | |||
<ReferencePackSharedFxVersion Condition="'$(VersionSuffix)' != ''">$(ReferencePackSharedFxVersion)-$(VersionSuffix)</ReferencePackSharedFxVersion> | |||
<ReferencePlatformManifestOutputPath>$(ArtifactsObjDir)ref\PlatformManifest.txt</ReferencePlatformManifestOutputPath> | |||
<ReferencePlatformManifestPath Condition="'$(IsServicingBuild)' != 'true'">$(PlatformManifestOutputPath)</ReferencePlatformManifestPath> |
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.
nit:
<ReferencePlatformManifestPath Condition="'$(IsServicingBuild)' != 'true'">$(PlatformManifestOutputPath)</ReferencePlatformManifestPath> | |
<ReferencePlatformManifestPath>$(PlatformManifestOutputPath)</ReferencePlatformManifestPath> |
I generated this platform manifest based off of the 3.1.0 runtime pack. Checking it into the repo is sufficient for 3.1.2, since there is no "known good" platform manifest for 3.1.x that we can harvest and insert into the package. Replaces #17957. Copied from there:
I'll open an issue to track coming up with a better solution in case we need to service the targeting pack in the future - ideally a solution would be general across all repos that generate a targeting pack
CC @nguerrera @dagood @ericstj @Pilchie @JunTaoLuo @jkotalik @dougbu