Skip to content

ci(release): enforce release-note policy - #75

Merged
lefoulkrod merged 2 commits into
mainfrom
codex/release-notes-policy
Aug 16, 2026
Merged

lefoulkrod merged 2 commits into
mainfrom
codex/release-notes-policy

Conversation

@lefoulkrod

Copy link
Copy Markdown
Contributor

What changed

  • document the organization release-note and Conventional Commit policy
  • require every PR to add a validated visitor-facing fragment or explicitly opt out
  • add a tested fragment validator and Keep a Changelog draft generator
  • add a dedicated release-note-policy workflow

Why

Site and documentation outcomes should be recorded when their PR is reviewed instead of reconstructed from commit history later.

How it was tested

  • node --test tests/release-notes.test.mjs
  • node scripts/release-notes.mjs validate-fragments
  • ./arbor build
  • actionlint on the new workflow

Release note

None: Adds contribution and release-process enforcement; published site content is unchanged.

@lefoulkrod lefoulkrod added the release-note:none No externally visible release note; PR body must explain why label Aug 16, 2026
@lefoulkrod
lefoulkrod marked this pull request as ready for review August 16, 2026 23:12
@lefoulkrod
lefoulkrod merged commit eda7b92 into main Aug 16, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-note:none No externally visible release note; PR body must explain why

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant