Create or update RELEASES.md documenting CNCF project release processes.
npx skills add https://github.com/castrojo/cncf-skills --skill releases
Please help me install this Agent Skill. Skill: releases Source: https://github.com/castrojo/cncf-skills/tree/main/skills/releases Command: npx skills add https://github.com/castrojo/cncf-skills --skill releases
This Skill helps CNCF projects establish or improve their release documentation, ensuring transparency, consistency, and ease of onboarding for new contributors by creating a comprehensive RELEASES.md file.
RELEASES.md file that covers all required aspects, including versioning, cadence, supported versions, release authority, a step-by-step checklist, publication locations, and artifact verification.Use the releases skill to create a new RELEASES.md file in the repository root, documenting the project's versioning scheme, release cadence, and artifact publication locations.
High-intent search queries and answers about installing and using this skill.
To document a CNCF project release process, generate a RELEASES.md file covering versioning schemes, release cadence, supported versions, and artifact publication locations. This ensures transparency and eases onboarding for new contributors.
A release management checklist should include end-to-end release steps, artifact signing procedures, publication locations, and verification methods. It must also ensure consistency with SECURITY.md and MAINTAINERS.md files.
You need a formal RELEASES.md file for versioning when your CNCF project is preparing for graduation or needs to establish transparency, consistency, and a well-defined release authority for release managers.
To formalize artifact signing and publication locations, document the specific verification methods and publication repositories within your RELEASES.md file. This standardizes the process and enhances project transparency.
Yes, you can align release documentation with SECURITY.md and MAINTAINERS.md. The generated RELEASES.md file ensures consistency across these governance documents to maintain comprehensive project standards.
mcj-coderPlan software releases with semantic versioning and changelog documentation.
SAP-samplesAutomate CAP change workflows for CDS definitions, handlers, and artifact regeneration.
fyrsmithlabsValidate repository naming, structure, documentation, and security files against project standards.
neolaoAutomate version bumps, CHANGELOG updates, documentation regeneration, and commit/tagging with Semantic Versioning.