ci: migrate original NuGet release to the shared Gitea channel #35
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: KofTwentyTwo/AppKit#35
Reference in new issue
Block a user
One CI-only thin caller for the original AppKit v* release, using the protected shared kof-release-v1 channel. Shared implementation retains original locked Windows build/tests/coverage/pack, per-package SBOMs, checksums, bound forge evidence and isolated own-token release asset publication; registry credentials never enter build jobs. Application source/version/dependencies are unchanged.
Actual representative3800/job56467 succeeded with original SDK100 and eight retained package/symbol assets; no new product tag or release was created. Original GitHub release38057132269 confirms actual NuGet publication of the four existing AppKit IDs.
DRAFT activation hold: finish exact existing publisher READ163, four-package-only NuGet key delivery/renewal and explicit replacement of hosted GitHub attestation/immutability guarantees with honest forge-bound records. No key/grant/runtime enrollment or main tag route is enabled by this proposal. No Authenticode/Azure requirement, unused template key or GUI6219 dependency is added.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.