fix: skip the missing-baseline warning when from is set - #1789

…first release

## What/Why

Release Drafter v7.8.0 appends a "without a comparison baseline"
warning to a first release even when `from` supplied the baseline. A
temporary step removes that block from the draft until a Release
Drafter release includes release-drafter/release-drafter#1789.

## Proof it works

bats scripts/tests/ passes (53 tests, 11 for the new script). The
removal regex leaves the notes intact on the real body from a test
repository's first release. shellcheck, actionlint, the drift check,
and pre-commit pass.

## Risk

Low. The step makes no API calls unless `from` is set, and leaves any
body without that exact warning untouched.

## AI role

Claude Opus 5.5 wrote the step and tests. A human reviews them.

## Review focus

The regex that bounds the warning block.

Signed-off-by: jmeridth <jmeridth@gmail.com>

…rkaround

## What/Why

Release Drafter v7.9.0 includes release-drafter/release-drafter#1789,
so it no longer adds the missing-baseline warning when `from` is set.
Bump the pins to v7.9.0 and remove the temporary step, script, tests,
and docs sentence that stripped the warning.

## Proof it works

bats scripts/tests/ passes (42 tests). shellcheck, actionlint, the
drift check, and pre-commit pass. v7.9.0's other changes are
backward compatible: autolabeler sync-labels defaults to false, and
single `label:` rules still validate.

## Risk

Low. Removes a workaround the new pin makes unnecessary.

## AI role

Claude Opus 5.5 made the change. A human reviews it.

## Review focus

None.

Signed-off-by: jmeridth <jmeridth@gmail.com>

#206)

* feat(release): fill first-release notes from GitHub generated notes

## What/Why

Release Drafter v7 returns no pull requests when the repository has no
published release, so every first release shipped with "No changes".
The create_release job now checks for a published release before the
draft. When there is none, it asks GitHub's generate-notes API for notes
on the tag and writes them into the draft body. The job's body output
uses the new body, so release discussions match. Later releases keep the
Release Drafter body.

The logic lives in scripts/has-published-release.sh and
scripts/first-release-notes.sh with bats tests. Both release-draft.yaml
and release.yaml carry inline copies, and test-scripts checks them for
drift.

## Proof it works

- bats scripts/tests/ passes (49 tests, 18 new).
- shellcheck, the inline-copy drift check, actionlint, and pre-commit
  all pass.
- has-published-release.sh returns true against this repository and
  false against a repository with no releases, and fails on a 404.

## Risk

Medium. It adds two API calls to every release and a body rewrite on
first releases. A failed call stops the release before tags are pushed.

## AI role

Claude Opus 5.5 wrote the change. A human reviews it.

## Review focus

- Failing the job when generate-notes or the PATCH fails, instead of
  falling back to the "No changes" body.
- Truncating bodies over GitHub's 125,000 character limit.

Signed-off-by: jmeridth <jmeridth@gmail.com>

* feat(release): list every pull request on a first release with `from`

## What/Why

Release Drafter v7.8.0 added a `from` input that sets the comparison
baseline even when no published release exists. On a first release,
pass the repository's root commit as `from`, so the notes list every
merged pull request with the caller's categories and templates. This
replaces the GitHub generated notes fallback and its PATCH call.

## Proof it works

bats scripts/tests/ passes (42 tests, 11 for first-release-base.sh,
covering several roots, shallow clones, and API errors). shellcheck,
actionlint, the inline-copy drift check, and pre-commit pass.

## Risk

Medium. Bumps Release Drafter from v7.7.0 to v7.8.0, a large internal
restructure, in the release and auto-labeler workflows. Later releases
behave as before because `from` is empty when a published release
exists.

## AI role

Claude Opus 5.5 wrote the change after a Release Drafter maintainer
pointed at the `from` input. A human reviews it.

## Review focus

The v7.8.0 bump, and the root commit choice when a repository has
several roots.

Signed-off-by: jmeridth <jmeridth@gmail.com>

* fix(release): remove Release Drafter's missing-baseline warning on a first release

## What/Why

Release Drafter v7.8.0 appends a "without a comparison baseline"
warning to a first release even when `from` supplied the baseline. A
temporary step removes that block from the draft until a Release
Drafter release includes release-drafter/release-drafter#1789.

## Proof it works

bats scripts/tests/ passes (53 tests, 11 for the new script). The
removal regex leaves the notes intact on the real body from a test
repository's first release. shellcheck, actionlint, the drift check,
and pre-commit pass.

## Risk

Low. The step makes no API calls unless `from` is set, and leaves any
body without that exact warning untouched.

## AI role

Claude Opus 5.5 wrote the step and tests. A human reviews them.

## Review focus

The regex that bounds the warning block.

Signed-off-by: jmeridth <jmeridth@gmail.com>

* fix(release): keep the draft's tag when removing the baseline warning

## What/Why

A PATCH to a draft release without tag_name resets its tag to an
"untagged-" placeholder, so the end-to-end test published the release
under that tag. Send tag_name, name, and target_commitish back with the
new body.

## Proof it works

bats scripts/tests/ passes (54 tests), including a new check that the
PATCH carries the tag, name, and target. The drift check, actionlint,
shellcheck, and pre-commit pass.

## Risk

Low. Same step, more fields in one PATCH.

## AI role

Claude Opus 5.5 found the bug in an end-to-end test and fixed it. A
human reviews it.

## Review focus

None.

Signed-off-by: jmeridth <jmeridth@gmail.com>

* feat(release): bump Release Drafter to v7.9.0 and drop the warning workaround

## What/Why

Release Drafter v7.9.0 includes release-drafter/release-drafter#1789,
so it no longer adds the missing-baseline warning when `from` is set.
Bump the pins to v7.9.0 and remove the temporary step, script, tests,
and docs sentence that stripped the warning.

## Proof it works

bats scripts/tests/ passes (42 tests). shellcheck, actionlint, the
drift check, and pre-commit pass. v7.9.0's other changes are
backward compatible: autolabeler sync-labels defaults to false, and
single `label:` rules still validate.

## Risk

Low. Removes a workaround the new pin makes unnecessary.

## AI role

Claude Opus 5.5 made the change. A human reviews it.

## Review focus

None.

Signed-off-by: jmeridth <jmeridth@gmail.com>

---------

Signed-off-by: jmeridth <jmeridth@gmail.com>