Files
AgriciDaniel 234c8e595c chore(repo): declutter root by relocating community and secondary docs
Move CODE_OF_CONDUCT.md, CONTRIBUTING.md, SECURITY.md, and SUPPORT.md to
.github/ (GitHub still surfaces the Contributing / Code of conduct / Security
tabs), and RELEASE_CHECKLIST.md, PRIVACY.md, CONTRIBUTORS.md, and TODO.md to
docs/. Root drops from 26 to 18 files. Update every live reference (README,
docs, PR template, CLAUDE.md tree, NOTICE), the lint_prose root basename list,
and the SECURITY.md path in tests. Required files (LICENSE, NOTICE, CITATION.cff,
pyproject.toml, installers, lockfiles, dotfiles) stay at root.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-09 01:39:42 +03:00

1.3 KiB

Release Checklist

Use this before publishing a claude-blog release.

Versioning

  • Version is coherent in .claude-plugin/plugin.json, pyproject.toml, README.md, and CHANGELOG.md.
  • CHANGELOG.md has a dated section for the release.
  • README install examples point at the intended repo and release ref.
  • Installer hashes in README match the committed install.sh and install.ps1.

Validation

  • python3 scripts/lint_prose.py passes.
  • python3 -m pytest tests/ -q passes when scripts or tests changed.
  • claude plugin validate . passes on a machine with Claude Code installed.
  • CI is green on the protected branch.

Installer Smoke Test

  • Unix installer works in a temporary HOME.
  • Windows installer works in a temporary profile.
  • Nested skill payloads are present after install, including FLOW prompt references and Google report templates.
  • Unix uninstall removes only paths from the claude-blog manifest or package allowlist.
  • Shared credentials under ~/.config/claude-seo are not deleted by uninstall.

Publishing

  • Marketplace metadata points at the intended owner and repository.
  • Release notes include security or audit remediation highlights.
  • Create and push the release tag only after all checks pass.