fix(release): bound release commit lookups

[waleedlatif1]

Summary

• Bound release commit lookups and anchor CI releases to the exact commit being built.
• Preserve changelog categories, contributor credits, and the existing publication flow.

Type of Change

• Bug fix

Testing

Seven regression tests pass, covering large histories, detached checkouts, older releases, merge ancestry, and release-title parsing. Lint, all 46 repository audits, and docs-manifest validation pass.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Sep 10, 2026 9:03am UTC

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge with no actionable correctness, security, or repository-rule issues identified.

Summary

• Replaces shell-string Git execution with argument-safe execFileSync calls.
• Searches release boundaries incrementally along first-parent history.
• Uses the validated CI commit as the current release anchor.
• Adds regression coverage for large histories, detached checkouts, ancestry, and release-title parsing.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
    CI[Main-branch release push] --> SHA[GITHUB_SHA]
    SHA --> Validate[Validate requested version against commit subject]
    Validate --> Current[Current release commit]
    Current --> History[Search first-parent release history]
    History --> Previous[Previous release commit]
    Previous --> Range[Generate changelog commit range]
    Range --> Publish[Publish GitHub release]

Loading

_{Reviews (1) · Last reviewed commit: "fix(release): bound release commit looku..."}