Skip to content

Conversation

@NikolaMilosavljevic
Copy link
Member

Contributes to: dotnet/source-build#3224

This dependency is needed for source-build PVP flow, which was enabled for razor with dotnet/installer#16495

Fix for ttps://github.com/dotnet/source-build/issues/3224 will enable razor to consume live runtime and aspnetcore packages, during product source-build.

@NikolaMilosavljevic NikolaMilosavljevic requested review from a team as code owners June 8, 2023 18:43
@NikolaMilosavljevic
Copy link
Member Author

@mmitche @dotnet/source-build-internal @MichaelSimons @oleksandr-didyk

but are present in Version.Details.xml for source-build PVP flow. See the comment in Version.Details.xml for more information.
-->
<MicrosoftExtensionsObjectPoolPackageVersion>6.0.0</MicrosoftExtensionsObjectPoolPackageVersion>
<SystemCollectionsImmutablePackageVersion>6.0.0</SystemCollectionsImmutablePackageVersion>
Copy link
Member

@jaredpar jaredpar Jun 8, 2023

Choose a reason for hiding this comment

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

This repo needs to be on SCI 7.0, not 6.0. What happens when we fix that?

Copy link
Member Author

Choose a reason for hiding this comment

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

It is currently on 6.0.0 - I'm only moving the property to a different group within the file.

Should update to SCI 7.0.0 be part of a separate PR?

Copy link
Member

Choose a reason for hiding this comment

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

I think Jared is asking what will be the impact to source-build of upgrading it?

Copy link
Member Author

@NikolaMilosavljevic NikolaMilosavljevic Jun 9, 2023

Choose a reason for hiding this comment

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

No impact on source-build - it always picks the latest live version anyway - 8.0.x.

However, due to recent improvements in source-build infra, all those dependencies need to be expressed in Version.Details.xml. As this particular dependency is not automatic (no maestro subscription) there isn't even a need to keep this version in Version.Details.xml and 'Versions.props`, in sync - it would be nice to do that though.

Copy link
Member

@333fred 333fred left a comment

Choose a reason for hiding this comment

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

@jaredpar any further comments on your end?

@333fred 333fred enabled auto-merge (squash) June 12, 2023 17:57
@333fred 333fred merged commit 3e59026 into dotnet:main Jun 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants