-
Notifications
You must be signed in to change notification settings - Fork 134
Update package category in VMR repos #5070
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
Labels
Comments
ViktorHofer
added a commit
to dotnet/symreader
that referenced
this issue
Apr 23, 2025
ViktorHofer
added a commit
to microsoft/vstest
that referenced
this issue
Apr 23, 2025
See dotnet/source-build#5070 Also remove unnecessary PublishingVersion property.
ViktorHofer
added a commit
to ViktorHofer/NuGet.Client
that referenced
this issue
Apr 23, 2025
3 tasks
ViktorHofer
added a commit
to dotnet/roslyn
that referenced
this issue
Apr 23, 2025
See dotnet/source-build#5070 Also remove the unnecessary PublishingVersion property.
akoeplinger
pushed a commit
to dotnet/symreader
that referenced
this issue
Apr 23, 2025
nohwnd
pushed a commit
to microsoft/vstest
that referenced
this issue
Apr 23, 2025
See dotnet/source-build#5070 Also remove unnecessary PublishingVersion property.
akoeplinger
pushed a commit
to dotnet/roslyn
that referenced
this issue
Apr 23, 2025
See dotnet/source-build#5070 Also remove the unnecessary PublishingVersion property.
Closing as completed. Bits still need to flow into the VMR but that can happen asynchronously and doesn't need to be tracked. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Repositories that don't publish to dotnet10 feeds need to set the publishing category in their Publishing.props file so that their packages get published to the right feeds when getting built inside the VMR.
The text was updated successfully, but these errors were encountered: