skills.rest
dsully
dsullyCOMMUNITY
Explore all skills by this author →
Website𝕏@dsullyGitHub

release-checklist

Guide maintainers through the PKCS12 release process with version, changelog, tests, packaging, tagging, and CPAN upload.

9|15|Updated Feb 24, 2009
Search Tags:#testing#changelog#versioning#release#git tagging#cpan#dist-zilla
One-click install
npx skills add https://github.com/dsully/perl-crypt-openssl-pkcs12 --skill release-checklist-dsully
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-checklist
Source: https://github.com/dsully/perl-crypt-openssl-pkcs12/tree/main/.claude/skills/release-checklist
Command: npx skills add https://github.com/dsully/perl-crypt-openssl-pkcs12 --skill release-checklist-dsully

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken or incomplete releases by guiding you through every required checkpoint in the Crypt::OpenSSL::PKCS12 release workflow.

Core Features & Use Cases

  • Version gate verification: Confirms the module version in PKCS12.pm matches the intended release version.
  • Release notes completeness: Ensures Changes.md includes the current version with today’s date and a meaningful summary.
  • Quality assurance execution: Runs the full test suite and then validates author tests with strict warnings enabled.
  • Distribution packaging and publishing: Builds the dist tarball with Dist::Zilla, creates and pushes the git tag, and uploads the release to CPAN.
  • Use case: Ideal for maintainers preparing a CPAN publish where you want a predictable, step-by-step checklist and a clear stop-on-failure workflow.

Quick Start

Use the release-checklist Skill to verify version, changelog, tests, dist build, tagging, and CPAN upload for the current Crypt::OpenSSL::PKCS12 release.

Frequently Asked Questions about release-checklist

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

FAQPage Schema
How do I release a Perl module to CPAN using Dist::Zilla?▼

To release a Perl module to CPAN, you validate the module version, update Changes.md, run standard and author tests, build the tarball with Dist::Zilla, push a git tag, and upload via dzil release.

What steps are required to publish a Crypt::OpenSSL::PKCS12 distribution?▼

Publishing a Crypt::OpenSSL::PKCS12 distribution requires verifying version alignment in PKCS12.pm, confirming Changes.md has today's date, running test suites, executing dzil build, tagging v<VERSION>, and uploading the tarball to CPAN.

Do I need to run author tests before uploading a CPAN tarball?▼

Yes, running author tests with strict warnings enabled is required before uploading a CPAN tarball to ensure code quality and prevent broken releases from passing through the standard test suite.

Can I stop the CPAN release process if the changelog is missing today's date?▼

Yes, the release checklist uses a stop-on-failure workflow that halts the CPAN release process if Changes.md lacks the current version entry with today's date and a meaningful summary.

Why does my Perl versioning fail the CPAN release gate?▼

Perl versioning fails the CPAN release gate when the module version in PKCS12.pm does not match the intended release version, which prevents mismatched artifacts from being packaged and uploaded.

Related Skills

Explore More Product & Management Skills→
JansenAnalyticsJansenAnalytics
5

release-manager

Automate changelog generation, version bumps, and GitHub releases via CLI.

Community
Intermediate
vercelvercel
26.1k

list-npm-package-content

List npm package tarball contents before publishing.

Official
Intermediate
cartridge-ggcartridge-gg
80

run-tests

Run the Cartridge Controller monorepo test suite across linting, unit, build, and E2E checks.

Official
Intermediate
oaldersoalders
4

working-with-dist-zilla

Manage build, testing, and release of CPAN distributions with Dist::Zilla.

Community
Intermediate