Skip to content

feat: add semantic releases and contributor tracking - #1

Merged
HashemKhalifa merged 5 commits into
mainfrom
fix/semantic-release
Aug 31, 2026
Merged

feat: add semantic releases and contributor tracking#1
HashemKhalifa merged 5 commits into
mainfrom
fix/semantic-release

Conversation

@HashemKhalifa

@HashemKhalifa HashemKhalifa commented Aug 31, 2026

Copy link
Copy Markdown
Owner

Details

What this PR does

  • Adds semantic-release with Conventional Commits based SemVer calculation.
  • Records the release version and grouped changelog in the release PR.
  • Verifies those merged release assets before creating Git tags and GitHub Releases.
  • Makes pnpm 11.11.0 the sole Node package manager for local and CI release tooling.
  • Adds CI gates for Python validators and the 52-test bundled pstack suite.
  • Adds explicit contributor and upstream provenance tracking.
  • Documents and enforces a PR-only release workflow with no direct commits to main.

How it works

  • semantic-release analyzes commits on main and selects major, minor, or patch releases.
  • The release PR carries the matching plugin manifest version and changelog entry.
  • The exec plugin fails closed if either release asset does not match semantic-release's calculated tag.
  • The GitHub plugin creates the verified tag and GitHub Release; it never writes a release commit to main.
  • CI runs before publication, and the retained live-agent receipt remains part of the port validation gate.

Validation

  • 13 Python tests passed, including a regression for linked semantic-release changelog headings.
  • Port validator passed for 45 skills and 5 agents.
  • Workflow YAML parsed successfully.
  • pnpm frozen-lockfile installation passed its supply-chain policy checks.
  • semantic-release dry run completed successfully and selected v1.0.0.
  • Generated release notes include Features and Bug Fixes sections.
  • Bundled pstack suite passed 52/52 tests and 206 assertions in the isolated CI Git environment.
  • All five custom agents passed live Codex 0.151.0 spawn checks.

Contributors

Release behavior

After this PR is accepted and merged, the Release workflow revalidates main, confirms the PR-recorded v1.0.0 assets, creates tag v1.0.0, and publishes the GitHub Release without bypassing branch protection.

Use semantic-release to derive SemVer from Conventional Commits, generate changelogs, synchronize plugin metadata, and publish GitHub Releases after validated main merges. Record upstream and port contributors from public path history.
Pin the Conventional Commits preset to the major supported by semantic-release's changelog writer so release-note generation completes deterministically.
Validate semantic-release's actual changelog heading format during prepare so the manifest sync, release commit, and tag lifecycle fail closed on real generated output.
@HashemKhalifa

Copy link
Copy Markdown
Owner Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Aug 31, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-08-31T12:23:19.519484Z 1b30640 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1b306400dc

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread plugins/pstack-codex/scripts/validate_release.py Outdated
Remove direct-main release commits, make pnpm the sole package manager, verify the release PR's version and changelog before tagging, and accept linked semantic-release headings.
Put version and changelog preparation before pull-request merge and document the exact manifest update command.
@HashemKhalifa
HashemKhalifa merged commit 13d3a6c into main Aug 31, 2026
1 check passed
@HashemKhalifa
HashemKhalifa deleted the fix/semantic-release branch August 31, 2026 12:46
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant