Move NuGet publishing to forge Actions #1
Loading…
Reference in a new issue
No description provided.
Delete branch "d/forge-publish"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
🤖 Claude AI Code Review
Summary
Migrates NuGet publishing from GitHub Actions to Gitea (forge) Actions, consolidating into a single tag-triggered workflow, plus TODO notes.
Code Quality ⭐⭐⭐⭐☆
Well-documented workflow with clear comments explaining the non-obvious Windows runner/UAC constraints.
Issues
🟡 publish.yml —
publish-mauiandpublish-basepublish independently but neither--skip-duplicatefailure is caught. More importantly, the old workflow had|| trueon base pushes; the new base loop lets a single push failure fail the whole job, which may leave partial publishes (some base packages up, some not) and MediaProcessing gated behind it. Confirm this is the intended stricter behavior.🟢 publish.yml —
runs-on: windows(bare label) instead ofwindows-latest. Ensure a self-hosted runner is actually registered with thewindowslabel, otherwise both MAUI and MediaProcessing jobs will hang unscheduled.🟢 publish.yml — the 10-minute fixed
Start-Sleepfor NuGet indexing is fragile; if indexing is slower the MediaProcessing restore fails. Not new to this PR (carried from old workflow), so non-blocking.No blocking bugs, secret leaks, or breaking issues. Just confirm the self-hosted
windowsrunner label exists before merging.📊 Tokens: 7428 input + 512 output | 💰 Cost: ~$0.0499
Generated by Claude Opus 4.8 via Gitea Actions