Use newer schema in nuspec when packing?
Open
Nobody has claimed this yet.
enhancement
nupkg spec
paket pack
sdk: dotnet/sdk
sdk: verbose sdk
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Today http://schemas.microsoft.com/packaging/2011/10/nuspec.xsd is used.
---------------------------
NuGet Package Explorer
---------------------------
The element 'metadata' in namespace 'http://schemas.microsoft.com/packaging/2011/10/nuspec.xsd'
has invalid child element 'repositoryUrl' in namespace 'http://schemas.microsoft.com/packaging/2011/10/nuspec.xsd'.
List of possible elements expected: 'iconUrl, summary, packageTypes, serviceable, copyright, references, frameworkAssemblies, requireLicenseAcceptance, repository, dependencies, description, contentFiles, tags, developmentDependency, releaseNotes, language'
in namespace 'http://schemas.microsoft.com/packaging/2011/10/nuspec.xsd'.
---------------------------
OK
---------------------------
Should we change to http://schemas.microsoft.com/packaging/2012/06/nuspec.xsd
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no source file or test. Start at the nuspec packing entry point and trace where the 2011/10 schema URL is selected; update the schema handling so repositoryUrl validates against the newer schema, then verify the packed nuspec with NuGet Package Explorer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100