Some checks failed
Publish packages / cultcache-py to PyPI (push) Has been cancelled
Publish packages / cultmesh-py to PyPI (push) Has been cancelled
Publish packages / cultnet-py to PyPI (push) Has been cancelled
Publish packages / @gamecult/cultcache-ts to npm (push) Has been cancelled
Bumps org.gamecult.cultlib to 1.0.57 and rebuilds its managed plugins from main, so the Unity package carries the store-routing CultCache (one home store per type, AddBackingStore(CacheBackingStore, Type[]), atomic commit) instead of the Sep 3 assemblies. Install docs point at the new tag. The build script now publishes without Source Link or the source revision, with CI path mapping and cleared Release intermediates. The previous DLLs named the commit and the worktree they were built in, so committed plugins could never match a fresh build of the commit that holds them. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
23 lines
894 B
Markdown
23 lines
894 B
Markdown
# NuGet Packaging
|
|
|
|
CultLib publishes the managed dependency graph as separate packages. The leaf
|
|
package is `GameCult.Mesh`; its NuGet dependencies preserve the CultMesh,
|
|
CultNet, and CultCache ownership boundaries.
|
|
|
|
```powershell
|
|
powershell -ExecutionPolicy Bypass -File .\scripts\pack-nuget.ps1
|
|
```
|
|
|
|
The command creates a local feed under `artifacts/nuget`, verifies that every
|
|
internal dependency package exists at the same version, then restores and runs
|
|
a clean .NET consumer using only `PackageReference Include="GameCult.Mesh"`.
|
|
|
|
The Unity distribution remains `org.gamecult.cultlib`, built by
|
|
`scripts/build-unity-package.ps1`, because Unity consumes the managed assembly
|
|
closure through UPM rather than NuGet restore.
|
|
|
|
Install the Unity package from the immutable release tag:
|
|
|
|
```text
|
|
https://github.com/GameCult/CultLib.git?path=/unity/org.gamecult.cultlib#cultlib-unity-v1.0.57
|
|
```
|