Publish and finalize NuGet packages and GitHub releases.
Install
mkdir -p .claude/skills/release-publish && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2987" && unzip -o skill.zip -d .claude/skills/release-publish && rm skill.zipInstalls to .claude/skills/release-publish
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Publish SkiaSharp packages and finalize the release. Use when user says "publish X", "finalize X", "tag X", or "finish release X". This is the FINAL step - after release-testing passes. Publishes to NuGet.org, creates tag, GitHub release, and closes milestone. Triggers: "publish the release", "push to nuget", "create github release", "tag the release", "close the milestone", "annotate release notes", "testing passed what's next", "finalize 3.119.2", "release is ready".Key capabilities
- →Publish packages to NuGet.org
- →Create and push git tags
- →Generate GitHub releases
- →Close version-specific milestones
How it works
It executes a multi-step pipeline to publish packages, tag the repository, update release notes, and close milestones.
Inputs & outputs
When to use release-publish
- →Publish package to NuGet
- →Finalize the release process
- →Create a git tag and release
About this skill
Release Publish
Publication and Finish need separate explicit authorization. A maintainer can authorize a conditional Finish beforehand, but must still confirm the reviewed Finish plan. Neither follows automatically from Prepare or Build/Tests.
Push the packages
Before triggering:
- Run
audit-release-state.ps1 -Version A.B -Jsonfor the requestedrelease/<identity>. Require its exact-tipskiasharp-package (1642)build to have succeeded with one BAR, and the resource-triggeredskiasharp-tests (1630)run to have succeeded for the same branch, commit and build number with a matchingtriggerInfo.pipelineId. The producing Build/Tests runs and BAR are the release-validation evidence; do not require a separate local approval report. Never borrow.x,main, or PR evidence. - Derive the shipping SkiaSharp/HarfBuzzSharp ID/version set from the shipment's
source
scripts/VERSIONS.txtand pack filter. Check public availability, provenance, and existing publisher runs' resolvedskiaSharpBuildresources. Monitor an existing publication of the same producer; do not duplicate it. If the complete set is already public, do not republish. - Follow
Release Guide, step 4
for discovery and the Runs API request. Use dedicated publisher
skiasharp-nuget-release (1715), the exact producer Build number inresources.pipelines.skiaSharpBuild.version, and onlyarcade_shipping_signed. Request booleanvalidateOnly: falsefor production. Do not use the retired MAUI publisher or omit the producer selection.
After triggering:
- GET the admitted run; match publisher/tooling revisions and selected producer
run ID/build number. Read that producer to verify definition 1642, release
branch, source SHA and BAR. Normalize
validateOnlywhen checking read-back: Azure can return the requested boolean as the string"false". Stop on mismatched resources or parameters. - Check parent, isolated publisher and ESRP results, not aggregate status alone. Verify the live approval configuration; protected ESRP approval remains required. Preserve run/ESRP IDs and do not bypass approvals.
- Verify every expected public ID/version and source provenance. Missing packages can be propagation delay: keep monitoring without requeueing. Report failed or stalled publication with its evidence; do not retry failed parent jobs or switch paths. Monitoring-only requests do not authorize repairs.
Finish after the packages are public
Once the complete exact package set is public, use Release - Finish on
main, first with push=false to inspect the read-only plan. Resolve an
abbreviated prerelease identity to one exact public version; stop if ambiguous.
Present the source commit, exact tag, release title, support updates and
milestone changes to the user and obtain separate confirmation before
dispatching the same inputs with push=true:
gh workflow run release-finish.yml --repo mono/SkiaSharp --ref main \
-f version=4.153.0-preview.1 -f push=false
# After the plan is reviewed and separately approved:
gh workflow run release-finish.yml --repo mono/SkiaSharp --ref main \
-f version=4.153.0-preview.1 -f push=true
Inspect both workflow runs; do not treat dispatch as success. Finish verifies the public package's branch and commit, publishes the exact tag and GitHub Release, and coordinates support, release notes, and milestones. Rerun the read-only audit afterward. Never move a tag or replace a public package.
Local Finish fallback
Only when the GitHub workflow is unavailable or local execution is explicitly requested, use the repository-owned Finish script:
./scripts/infra/publishing/finish-release.ps1 -Version 4.153.0-preview.1 -Mode DryRun
# After reviewing the plan and receiving confirmation:
./scripts/infra/publishing/finish-release.ps1 -Version 4.153.0-preview.1 -Mode Push
Local Finish does not replace the dedicated publisher or protected ESRP approval. Do not use it to bypass a failed workflow.
When not to use it
- →Before release testing passes
- →When modifying protected branches directly
Prerequisites
Limitations
- →Cannot undo publishing to NuGet
- →Requires strict adherence to semver ordering
How it compares
It automates the final release steps, replacing manual publishing and repository management.
Compared to similar skills
release-publish side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| release-publish (this skill) | 1 | 4mo | Review | Advanced |
| gcp-cloud-run | 5 | 8mo | Review | Intermediate |
| flow-nexus-platform | 6 | 8mo | Review | Beginner |
| smithery-mcp-deployment | 8 | 1y | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by mono
View all by mono →You might also like
gcp-cloud-run
aj-geddes
Deploy containerized applications on Google Cloud Run with automatic scaling, traffic management, and service mesh integration. Use for container-based serverless computing.
flow-nexus-platform
ruvnet
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges
smithery-mcp-deployment
CaullenOmdahl
Best practices for creating, optimizing, and deploying MCP servers to Smithery. Use this skill when:(1) Creating new MCP servers for Smithery deployment(2) Optimizing quality scores (achieving 90/100)(3) Troubleshooting deployment issues (0/0 tools, missing annotations, low scores)(4) Migrating existing MCP servers to Smithery format(5) Understanding Smithery's schema format requirements(6) Adding workflow prompts, tool annotations, or documentation resources(7) Configuring smithery.yaml and package.json for deployment
deployment-pipeline-design
wshobson
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
vercel-deployment
davila7
Expert knowledge for deploying to Vercel with Next.js Use when: vercel, deploy, deployment, hosting, production.
netlify-deploy
openai
Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.