feat: publish releases after updating notes

[robjtede]

Summary

• Add --then-undraft to publish each GitHub release after its changelog notes update succeeds.
• Keep draft status unchanged by default and document the new option.
• Cover publishing, failed note updates, missing and empty changelogs, and argument handling.

Testing

• Not run (no test results provided).

Summary by CodeRabbit

• New Features
  • Added an optional setting to publish each release after its changelog notes are updated. Releases remain drafts by default.
  • Releases without a package changelog are skipped. If updating notes fails, that release is not published.
  • Releases with an empty changelog section can still be published using the existing fallback note.
  • Added command-line help and clearer errors for unrecognized options.

[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: 9e8e6df5-7860-4c6c-849e-0301276939dc

📥 Commits

Reviewing files that changed from the base of the PR and between c9728be and 304afe3.

📒 Files selected for processing (3)

• README.md
• release-tools/test.bash
• release-tools/update-release-notes.bash

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

---

📝 Walkthrough

Walkthrough

The release notes script now accepts --then-undraft to publish a release after its notes update succeeds. It also handles help and unknown options. Tests and README documentation cover the updated behavior.

Changes

Release notes update and publishing

Layer / File(s)	Summary
Option parsing and release update flow release-tools/update-release-notes.bash, release-tools/test.bash, README.md	The script handles help and unknown options, and publishes a release after updating its notes only when --then-undraft is set. Tests cover the option, failure cases, skipped releases, and fallback notes. The README describes the option and its behavior.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Feature

Merge Risk: ⚪ Minimal · up to 304af

No actionable issue was established with the opt-in publishing flow. The changes are mergeable after normal checks.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage		Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 2 files. (1 skipped: 1 …	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: publishing releases after updating their notes.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 2 files. (1 skipped: 1 unsupported.)

• Fix all pre-merge checks with AI

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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

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