release-publish

Publish SkiaSharp packages to NuGet.org and finalize releases.

5.5k|644|Updated Feb 22, 2016

Search Tags:#automation #github #release #publish #nuget #tag #skiasharp

Ready to run

npx skills add https://github.com/mono/SkiaSharp --skill release-publish-mono

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-publish
Source: https://github.com/mono/SkiaSharp/tree/main/.github/skills/release-publish
Command: npx skills add https://github.com/mono/SkiaSharp --skill release-publish-mono

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end release publishing workflow for SkiaSharp, ensuring packages are published, releases are created, and milestones are closed in a safe, auditable process.

Core Features & Use Cases

Automated package publishing to NuGet.org
Git tag creation and GitHub release generation
Milestone closure

Quick Start

Trigger the release-publish skill after confirming version numbers and release readiness to publish packages and finalize the release.

Frequently Asked Questions about release-publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I publish SkiaSharp packages to NuGet and finalize the GitHub release?▼

Publishing SkiaSharp packages to NuGet.org involves coordinating tag creation, GitHub release generation, and milestone closure while validating package availability and triggering CI pipelines.

How does automated release publishing work for SkiaSharp preview and stable versions?▼

Automated release publishing for SkiaSharp validates package availability, triggers CI pipelines, applies release notes, and coordinates tag creation and milestone closure for both preview and stable versions.

What is the best way to automate NuGet package publishing and milestone closure on GitHub?▼

The best way to automate NuGet publishing and milestone closure is using an end-to-end workflow that validates package availability, triggers CI pipelines, and applies release notes safely and auditably.

Do I need to trigger CI pipelines before creating a Git tag for a SkiaSharp release?▼

Yes, triggering CI pipelines is essential before creating a Git tag for a SkiaSharp release, as the workflow enforces package validation and applies release notes to ensure a safe, auditable process.

Why does my SkiaSharp release workflow fail to close the milestone after NuGet publishing?▼

Your SkiaSharp release workflow might fail to close the milestone if package availability validation fails or CI pipelines are not triggered successfully, as the process enforces a safe, auditable release sequence.