Skip to content

Release 0.11.0 - #43

Merged
mahach666 merged 1 commit into
mainfrom
release/0.11.0
Nov 13, 2026
Merged

mahach666 merged 1 commit into
mainfrom
release/0.11.0

Conversation

@mahach666

Copy link
Copy Markdown
Contributor

Release 0.11.0 on the released IOScene 0.1.0, so that the tag v0.11.0 publishes IfcIO, IfcIO.Cli and, for the first time, IfcIO.Scene.

What changes

  • Directory.Packages.props: IOScene [0.1.0-preview.2, 0.2.0-0) becomes [0.1.0, 0.2.0-0). IOScene 0.1.0 is on nuget.org; the pack-release.ps1 check that refuses a preview lower bound now passes.
  • Directory.Build.props: version 0.11.0.
  • CHANGELOG.md: ## [0.11.0] - 2026-11-13 with the entries that were under [Unreleased] (the IfcIO.Scene adapter and package, the world placement fix of fix: place IFC geometry in world coordinates and export GLB in metres, +Y up #35, the GLB units and axes, the frozen extras of docs: document frozen extras and their planned replacements #37), and an empty [Unreleased]. The package entry now names the range instead of saying it waits for IOScene 0.1.0.
  • README.md: version 0.11.0 in Limitations; the frozen-extras section no longer calls IfcIO.Scene and IOScene planned, and says that none of the replacements is published yet (the follow-up noted in docs: document frozen extras and their planned replacements #37).
  • docs/scene-adapter.md: the range [0.1.0, 0.2.0-0) instead of the preview range and the "a release fails on purpose" note.
  • CONTRIBUTING.md: the range [0.1.0, 0.2.0-0). Restore takes the lowest version in the range, now 0.1.0 from nuget.org, so a local package folder alone no longer builds against an unpublished IOScene; the paragraph now says to start the range at that version first (and to move the upper bound for a new minor).

No source or API changes.

Checks

  • dotnet restore, dotnet build IfcIO.slnx -c Release: 0 warnings, 0 errors; IOScene 0.1.0 restored from nuget.org with no other package source.
  • dotnet test IfcIO.slnx -c Release: IfcIO.Tests 149 passed (net10.0); IfcIO.Scene.Tests 19 passed and 1 skipped (the test that needs a configured IFC file) on net8.0 and net10.0.
  • tools/pack-release.ps1 (Windows PowerShell 5.1; the release job uses pwsh): exit 0. It builds the archives and IfcIO.0.11.0, IfcIO.Cli.0.11.0 and IfcIO.Scene.0.11.0; the IfcIO.Scene nuspec depends on IfcIO [0.11.0] and IOScene [0.1.0, 0.2.0-0) for net8.0 and net10.0, and both checks of the script pass.
  • Not run: the release workflow itself (it runs only on the tag) and the docs build (it runs in CI on this PR).

Notes

  • Found in review, not changed here: Directory.Build.props:38 turns on GenerateDocumentationFile only when IsPackable is true, but IsPackable is set later in src/IfcIO/IfcIO.csproj, so the IfcIO package has shipped without IfcIO.xml since the first release (IfcIO.Scene sets the property itself and has its XML file). Turning it on can raise new doc-comment warnings, which are errors here, so it is left for a later release.

After merge

Tag v0.11.0 on the merge commit. The CHANGELOG date is 2026-11-13; if the tag is pushed on a later day, the date should be corrected first.

IOScene is referenced as [0.1.0, 0.2.0-0) instead of the preview range, so the
release check on the IfcIO.Scene nuspec passes and the tag publishes the adapter.
Version 0.11.0; the changelog section 0.11.0 takes the entries of [Unreleased].
The README, CONTRIBUTING and the scene adapter page no longer describe IOScene
as a preview or the adapter as planned, and CONTRIBUTING says how to build
against an IOScene version that is not on NuGet.org now that restore takes 0.1.0
from there.
@mahach666
mahach666 merged commit b58a760 into main Nov 13, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant