Mark productVersion.txt as shipping artifact in 8.0 #64067
Merged
+2
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the issue where
productVersion.txt
andaspnetcore-productVersion.txt
were incorrectly marked as non-shipping artifacts in the ASP.NET Core 8.0 build configuration. These files are required in the final CDN locations and must be marked as shipping artifacts.Changes
Modified
eng/Publishing.props
to change theManifestArtifactData
property fromNonShipping=true
toNonShipping=false
for both:productVersion.txt
aspnetcore-productVersion.txt
This ensures these version files are properly included in the shipping manifest and published to the correct CDN locations alongside other shipping artifacts.
Impact
Without this change, the productVersion.txt files would not be available in the expected CDN locations, which could impact downstream consumers that rely on these files to determine the ASP.NET Core runtime version.
Fixes #[issue_number]
Original prompt
Fixes #64066
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.