Skip to content

Fix handling publishing cross-arch pack packages #15678

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

Merged
merged 1 commit into from
Mar 28, 2025

Conversation

jkoritzinsky
Copy link
Member

The handling for these paths had the wrong separator and was on the wrong side. Contributes to
dotnet/source-build#4984

Validated against the package listings from specific verticals

To double check:


These packages are always non-shipping, so only look there.
-->
<Artifact Include="$(ArtifactsNonShippingPackagesDir)**/VS.Redist.Common.*.$(TargetArchitecture).*.nupkg" IsShipping="false" Kind="Package" />
<Artifact Include="$(ArtifactsNonShippingPackagesDir)**/VS.Redist.Common.*.$(TargetArchitecture)-*.*.nupkg" IsShipping="false" Kind="Package" />
<Artifact Include="$(ArtifactsNonShippingPackagesDir)**/VS.Redist.Common.*.*_$(TargetArchitecture).*.nupkg" IsShipping="false" Kind="Package" />

Choose a reason for hiding this comment

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

Would we ever have packages with the old naming model, i.e. does it make sense to keep both patterns?

Copy link
Member Author

Choose a reason for hiding this comment

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

No we won't. I misread the pattern when I added this and got it wrong.

@jkoritzinsky jkoritzinsky enabled auto-merge (squash) March 28, 2025 03:06
@jkoritzinsky jkoritzinsky merged commit bef5823 into dotnet:main Mar 28, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants