fix(dotnet): use snupkg format for dotnet symbol packages#830
Merged
mergify[bot] merged 1 commit intomasterfrom Sep 30, 2019
Merged
fix(dotnet): use snupkg format for dotnet symbol packages#830mergify[bot] merged 1 commit intomasterfrom
mergify[bot] merged 1 commit intomasterfrom
Conversation
The legacy format is not supported by NuGet's own symbols server, and the SymbolSource server is currently experiencing a certificate expiration event, which seems to be a somewhat recurring issue (NuGet/Home#6082). More info: https://docs.microsoft.com/en-us/nuget/create-packages/symbol-packages-snupkg
rix0rrr
approved these changes
Sep 30, 2019
Collaborator
rix0rrr
left a comment
rix0rrr
left a comment
There was a problem hiding this comment.
When releasing, please cherry-pick this into a patch release, so we don't bring in new features when trying to unblock the CDK pipeline.
Collaborator
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Contributor
|
Thank you for contributing! ❤️ I will now look into making sure the PR is up-to-date, then proceed to try and merge it! |
RomainMuller
added a commit
that referenced
this pull request
Sep 30, 2019
The legacy format is not supported by NuGet's own symbols server, and the SymbolSource server is currently experiencing a certificate expiration event, which seems to be a somewhat recurring issue (NuGet/Home#6082). More info: https://docs.microsoft.com/en-us/nuget/create-packages/symbol-packages-snupkg
RomainMuller
added a commit
that referenced
this pull request
Sep 30, 2019
The legacy format is not supported by NuGet's own symbols server, and the SymbolSource server is currently experiencing a certificate expiration event, which seems to be a somewhat recurring issue (NuGet/Home#6082). More info: https://docs.microsoft.com/en-us/nuget/create-packages/symbol-packages-snupkg
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The legacy format is not supported by NuGet's own symbols server, and the
SymbolSource server is currently experiencing a certificate expiration event,
which seems to be a somewhat recurring issue (NuGet/Home#6082).
More info: https://docs.microsoft.com/en-us/nuget/create-packages/symbol-packages-snupkg
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.