Skip to content

build: consume *Sharp from nuget.org (Chrison.*) — org-migration P6 - #289

Merged
ChrisonSimtian merged 1 commit into
mainfrom
feat/p6-nuget-consumer-switch
Jul 23, 2026
Merged

build: consume *Sharp from nuget.org (Chrison.*) — org-migration P6#289
ChrisonSimtian merged 1 commit into
mainfrom
feat/p6-nuget-consumer-switch

Conversation

@ChrisonSimtian

Copy link
Copy Markdown
Collaborator

Repoints the Homelab engine + PowerOrchestrator from the Chrison-dev GitHub-Packages feed to the public nuget.org Chrison.* packages (published via Trusted Publishing from the *Sharp repos). This is P6 of the org-migration epic (#282) and removes the last cross-org GitHub-Packages coupling — the *Sharp NuGet feed is now fully decoupled from any GitHub org.

Changes

  • Infrastructure/engine/Homelab.Infrastructure.csprojProxmoxSharp 0.2.0-preview.31 → Chrison.ProxmoxSharp 0.2.0-preview.5; UnifiSharp 0.1.0-preview.27 → Chrison.UnifiSharp 0.1.0-preview.2.
  • PowerOrchestrator.Core.csproj — same IDs (ProxmoxSharp pinned exact; UnifiSharp stays -preview.*).
  • nuget.config — drop the Chrison-dev GitHub-Packages feed + its credentials/mapping. Chrison.* resolves from nuget.org (the old bare-ProxmoxSharp collision workaround is moot now that our IDs carry the Chrison.* prefix). Fallout-build feed unchanged.
  • Docs/commentsCLAUDE.md install command → Chrison.ProxmoxSharp.Cli; build/README.md + the discover-drift.yml note updated (packages are public on nuget.org).

No code changes — assembly names/namespaces stay ProxmoxSharp/UnifiSharp, so using statements are untouched.

Verified locally

dotnet restore + Release build of both the engine and the full PowerOrchestrator solution succeed (0 errors) resolving Chrison.* from nuget.org.

Not in this PR

  • The vendor/*Sharp submodule pointers still reference pre-Fallout commits (they're vendored for dogfooding, not the consumption path — packages are). Optional follow-up to bump them.
  • The org move itself (Chrison-devChrison-Homelab, Migrate Homelab repos into a dedicated Chrison-Homelab org #282 P1–P8) is separate.

…ion P6

Repoint the engine + PowerOrchestrator from the Chrison-dev GitHub-Packages feed
to the public nuget.org Chrison.* packages (published via Trusted Publishing from
the *Sharp repos). Decouples the NuGet feed from the GitHub org — P6 of the
Chrison-dev → Chrison-Homelab migration (#282), and removes the last cross-org
GitHub-Packages coupling.

- Homelab.Infrastructure.csproj: ProxmoxSharp 0.2.0-preview.31 → Chrison.ProxmoxSharp
  0.2.0-preview.5; UnifiSharp 0.1.0-preview.27 → Chrison.UnifiSharp 0.1.0-preview.2.
- PowerOrchestrator.Core.csproj: same IDs (ProxmoxSharp pinned; UnifiSharp stays -preview.*).
- nuget.config: drop the Chrison-dev GitHub-Packages feed + its credentials/mapping.
  Chrison.* now resolves from nuget.org (the old bare-ID collision workaround is moot —
  our IDs carry the Chrison.* prefix). Fallout-build feed unchanged (still PAT-auth).
- Docs/comments: CLAUDE.md install cmd → Chrison.ProxmoxSharp.Cli; build/README + the
  discover-drift note updated (packages are public on nuget.org now).

Assembly names/namespaces are unchanged (ProxmoxSharp/UnifiSharp), so no code edits.
Verified locally: restore + Release build of the engine and the PowerOrchestrator
solution both succeed (0 errors) against the nuget.org packages.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@ChrisonSimtian
ChrisonSimtian merged commit 639c0d3 into main Jul 23, 2026
2 of 7 checks passed
@ChrisonSimtian
ChrisonSimtian deleted the feat/p6-nuget-consumer-switch branch July 23, 2026 04:01
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