Repository navigation
Recommend a range for IOScene that nuget.org accepts - #3
Merged
Merged
Conversation
nuget.org refuses a dependency bound such as 0.2.0-0: a bound with one prerelease label is checked by its legacy rule, under which the label must start with a letter. The release of IfcIO.Scene 0.11.0 failed on it. The README and section 5 of the contract now recommend [0.N.0, 0.N+1.0-0.0): two labels make the bound SemVer 2.0, and it keeps out every preview of the next line except 0.2.0-0, which IOScene does not publish. The key registry fixes the ifc: formats from IfcIO.Scene 0.11.1, its first release, and the changelog preamble says that a patch adds or fixes, as the contract does.
This was referenced Nov 13, 2026
docs: show the released IOScene, scene adapters and IOViewer 0.3.0 on the profile
IOExtend/.github#2
Merged
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
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 range that the README and the contract recommend,
[0.N.0, 0.N+1.0-0), cannot be published on nuget.org. This changes it to[0.N.0, 0.N+1.0-0.0).Why
The release of IfcIO 0.11.0 failed at the push of
IfcIO.Scene, which depended onIOScene[0.1.0, 0.2.0-0):nuget.org checks every bound of a dependency range (NuGetGallery
ManifestValidator.ValidateDependencyVersion): a bound with metadata is refused, and a bound that is not SemVer 2.0 (one prerelease label) must match^\d+(\.\d+){0,3}(-[a-z][0-9a-z-]*)?$, so its label must start with a letter.0.2.0-0has one label,0.0.2.0-0.0has two, so it is checked as SemVer 2.0 and accepted, and it still keeps out every 0.2.0 preview except0.2.0-0, which nuget.org accepts only with build metadata and IOScene does not publish.What changes
README.md: the range, the examplePackageReference, the NU5104 note, and one sentence on why the bound has two labels.docs/contract.md, section 5:[0.N.0, 0.N+1.0-0.0), and[1.M.0, 2.0.0-0.0)from 1.0.docs/keys.md: theifc:formats are fixed fromIfcIO.Scene0.11.1, its first release (nuget.org refused 0.11.0).CHANGELOG.md: Fixed entries under [Unreleased]; the preamble says that a patch adds or fixes, as section 5 of the contract does.Documentation only. The README inside the published 0.1.0 package keeps the old range until the next release.
Checks
[0.1.0, 0.2.0-0)(as nuget.org did) and accepts[0.1.0, 0.2.0-0.0)and[1.0.0, 2.0.0-0.0);[0.1.0, 0.2.0-0.0)is satisfied by 0.1.x and not by 0.2.0-preview.1, -alpha, -rc.1 or 0.2.0.pack-release.ps1passes (IOExtend/IfcIO and IOExtend/RvtIO PRs).