Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

## What/Why

The release body gets the "could not find a previous published release
... without a comparison baseline" block whenever no last release
exists, even when the caller passed `from` and Release Drafter compared
against it. Warn only when there is neither a last release nor `from`.

## Proof it works

npm run ci passes. The `from` without a release test now asserts the
body has no warning, and fails without the fix. A new test keeps the
warning when neither `from` nor a release exists.

## Risk

Low. One condition in the body template.

## AI role

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

## Review focus

Whether any caller relies on the warning appearing with `from` set.

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

…1785)

* feat(autolabeler): support multiple labels, stop rules and fallback

* feat(autolabeler): use labels with scalar label compatibility

* refactor(autolabeler): shorten fallback-label option name

* feat(autolabeler): configure fallback labels through an explicit rule

Add optional sync-labels configuration to remove stale managed labels while preserving unrelated labels. Honor multiple labels, stop rules, fallback selection and dry runs.

Assisted-by: Codex

Co-authored-by: release-drafter-releaser[bot] <336630105+release-drafter-releaser[bot]@users.noreply.github.com>