Stop the meta-package packing an empty symbol package - #50
Merged
Conversation
The 4.1.0 publish pushed fifteen packages and then failed: nuget.org returns 400 for a symbol package containing no .pdb files, and the meta-package has no assembly to produce one. The repository packs symbols for everything by default, so this project has to opt out by name. The failure landed after real packages had already gone up, and the tag and GitHub Release steps run after publishing, so the run left nuget.org half-updated with no tag to show for it. Pushing is idempotent (--skip-duplicate), so re-running completes it.
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
1 participant
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 4.1.0 publish pushed 15 packages then failed with
400 (The package does not contain any symbol (.pdb) files.)onHealthie.NET.4.1.0.snupkg. The meta-package has no assembly, so it has no PDB, but the repo packs symbols for everything by default — it has to opt out explicitly.Verified on a clean build (the first check was against a stale artefact): the project now emits a
.nupkgand no.snupkg.Publishing is
--skip-duplicate, so re-running the release completes the 6 packages that never went up and creates the tag and GitHub Release, which run after the publish step and so never happened.