[jjjermiah]

Closes #657. Evidence is in the commit body.

Summary by CodeRabbit

• Chores
  • Release note generation now skips changelog versions without matching tags and selects the first eligible tagged version as the previous release.
  • If the changelog’s linked previous version has no tag, release processing falls back to the newest valid earlier version tag.
  • Releases are rejected if no previous version can be identified or if the release version does not exceed it.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The release scripts now skip changelog version headings without matching tags. If the changelog-linked previous version has no tag, release.ts selects the newest valid semver tag below the release version or reports an error if none exists.

Changes: Release tag resolution

Layer / File(s)	Summary
Select an existing previous version .github/scripts/release-notes.ts, .github/scripts/release.ts	release-notes.ts scans later changelog headings for the first version with an existing tag. release.ts checks the linked tag and falls back to the newest valid semver tag below the release version. It fails if no fallback tag exists.

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

Change: Bug fix · Severity of issue fixed: Medium

Possibly related PRs

• jjjermiah/opencode-plugboard#649: Adds the [Unreleased] changelog content and version pin that the release workflow consumes.
• jjjermiah/opencode-plugboard#650: Adds the 0.65.0 changelog heading and compare link that lacked a matching tag.

Merge Risk: Low · up to 7b066

The release scripts now pick a previous version from tags that exist, which addresses the reported release failure. Before merging, the author should still add the pre-tag release-notes dry run and the missing-tag regression test requested in #657, and make the tag check namespace-safe. These gaps limit recurrence protection but are unlikely to cause a broken release on their own.

- [ ] Autofix · 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