build: Fallout CI + nuget.org Trusted Publishing (Chrison.* IDs)#12
Merged
Conversation
Mirror the ProxmoxSharp/UnifiSharp conversion for SynoSharp (hand-written client, no codegen): - build/: Fallout build project (Compile/Test/Pack/Publish) + build.sh/ps1 + .fallout/ root marker; new nuget.config adds the Fallout-build feed (Fallout.* only). - Rename package IDs to the Chrison.* prefix (Chrison.SynoSharp, Chrison.SynoSharp.Cli). AssemblyName/RootNamespace stay SynoSharp, so `using SynoSharp;` and the `synosharp` command are unchanged. - ci.yml → build+test only; publish.yml → NuGet/login@v1 OIDC → push to nuget.org (prerelease on main, stable on v* tag), job runs in the Nuget.org environment. - README: Build/Packages updated for Fallout + Chrison.* on nuget.org. Verified locally: ./build.sh Pack → 26 tests pass, emits Chrison.SynoSharp*.nupkg. Requires (repo setup): PACKAGES_PAT + NUGET_USER secrets, a Nuget.org GH environment, and a nuget.org Trusted Publishing policy for this repo + publish.yml (Environment=Nuget.org). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Mirrors the ProxmoxSharp (#20) / UnifiSharp (#14) conversion for SynoSharp: Fallout build/CI +
Chrison.*IDs + nuget.org Trusted Publishing (OIDC, keyless). Part of P0 for the org-migration epic (Chrison-dev/Homelab#282). SynoSharp is the simple case — hand-written client, no.Api/codegen.What changed
build/+build.sh/ps1+.fallout/marker); newnuget.configscopes the Fallout-build feed toFallout.*.Chrison.*IDs —Chrison.SynoSharp,Chrison.SynoSharp.Cli. AssemblyName/namespace staySynoSharp; thesynosharpcommand is unchanged. (The bareSynoSharpID is actually free on nuget.org, but we use theChrison.*prefix for consistency with the siblings.)ci.yml→ build+test;publish.yml→NuGet/login@v1OIDC → push (prerelease onmain, stable onv*), job runs in theNuget.orgenvironment.Verified locally
./build.sh Pack→ 26 tests pass, emitsChrison.SynoSharp{,.Cli}.nupkg.Setup (I've done the repo side)
PACKAGES_PAT+NUGET_USERsecrets and theNuget.orgenvironment are set. Needs you: create the nuget.org Trusted Publishing policy — ownerChrison-dev, repoSynoSharp, workflowpublish.yml, EnvironmentNuget.org(per our schema).Consumer updates (Homelab engine →
Chrison.SynoSharpfrom nuget.org) belong to the Homelab-side migration (#282, P6), not this PR.