Skip to main content
EVOKORE// SKILLS / release-process
Sign in
Workspace
Brutal Honesty Kitmarkdownsha 2BB1638B2D0D

release-process

documentation

Release Process

This page summarizes the public release process for Brutal Honesty Kit. The current release is v3.7.1.

Release Model

  • VERSION records the current release number.
  • v3.7.1/ is the current public release index.
  • v3.5/ remains the implementation path for v3.7.1 compatibility.
  • Historical folders remain available for migration and provenance.

See version-map.md.

Before Tagging

  1. Update public release notes and changelog material.
  2. Confirm the release index points at the correct implementation path.
  3. Run the focused release tests.
  4. Run schema-drift validation.
  5. Confirm docs only advertise surfaces that exist or are being published in the same release.

Focused release checks:

cd v3.5
python -m pytest tests/test_validate_pr_brutal_honesty.py tests/test_v371_loophole_replay.py tests/test_r79_severity_cap.py tests/test_r80_rewrite_scope.py tests/test_check_brutal_honesty_hook.py -v

Schema drift:

python v3.5/scripts/validate_v33_schema_drift.py

Public Release Checklist

The adapted public-release checklist is tracked at public-release-task-list.md.

That checklist records the playbook adaptation. It covers governance files, GitHub templates, CI, release creation, visuals, Pages, wiki publication, and social-preview work.

Wiki Publication

If GitHub Wiki remains enabled, publish the files in wiki-seed/ to the wiki repository. Keep those pages thin and link back to this docs tree to avoid drift.

release-process — Evokore Skills