fix(ci): prevent DCO failures on generated releases

[yordis]

• Generated releases need a sign-off matching the release bot's commit identity to satisfy DCO.
• Unblock release chore(main): release trogonstack-diataxis 0.1.0 #77 while preserving the repository's DCO requirements.

[cursor]

PR Summary

Low Risk
Single CI config string change with no runtime or security impact.

Overview
Updates the release-please signoff in .github/release-please-config.json so generated release commits use SHT Bot instead of Straw Hat Team Bot, while keeping the same sht-bot noreply email.

This aligns the configured sign-off with the bot’s actual commit identity so DCO checks pass on automated release PRs (e.g. unblocking release #77).

^{Reviewed by Cursor Bugbot for commit 407aa87. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 9d13ae98-b6c0-4a1f-b1d9-0c3a56d6373a

📥 Commits

Reviewing files that changed from the base of the PR and between d839032 and 407aa87.

📒 Files selected for processing (1)

• .github/release-please-config.json

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

Walkthrough

The release-please configuration changes the commit signoff name from “Straw Hat Team Bot” to “SHT Bot”. The email address remains unchanged.

Changes

Release commit signoff

Layer / File(s)	Summary
Update release signoff identity .github/release-please-config.json	The signoff value now uses SHT Bot with the existing email address.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to 407aa

The release signoff update matches the stated DCO objective and introduces no identified merge-blocking risk.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description clearly explains that the change aligns generated release sign-offs with the release bot identity to prevent DCO failures.
Title check	✅ Passed	The title accurately summarizes the main change: preventing DCO failures for generated releases.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch yordis/fix-release-dco

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit checks the bot’s new name
The signoff stamp now looks the same
The email stays in place
SHT Bot leads the release race
Quiet commits hop into fame}

_{Comment @coderabbitai help to get the list of available commands.}