Skip to content

Conversation

jkoritzinsky
Copy link
Member

Contributes to fixing failures mentioned in dotnet/install-scripts#586 (comment)

…" step so we don't need to munge them through the different runtime jobs
@Copilot Copilot AI review requested due to automatic review settings April 15, 2025 18:48
@ghost ghost added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Apr 15, 2025
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

Files not reviewed (1)
  • eng/Publishing.props: Language not supported
Comments suppressed due to low confidence (1)

eng/pipelines/runtime-official.yml:476

  • Confirm that removing the /p:ShouldGenerateProductVersionFiles parameter aligns with the new runtime mechanism for generating productVersion.txt files. If so, please update any related documentation to reflect this change.
buildArgs: -s mono.workloads -c $(_BuildConfig) -restore -build -publish /p:PackageSource=$(Build.SourcesDirectory)/artifacts/workloadPackages /p:WorkloadOutputPath=$(Build.SourcesDirectory)/artifacts/workloads /p:EnableDefaultRidSpecificArtifacts=false

@jkoritzinsky jkoritzinsky added area-Infrastructure and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Apr 15, 2025
Copy link
Contributor

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants