QQQ UI API 1.6.0 adds the shared BasicErrorResponseV1 schema to every
extension document. Regenerate release-notes.yaml and let the contract test
accept that core schema next to the ReleaseNotes*V1 schemas (additive).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
With the host's principal declared, detection, drafting and publishing
run as it instead of the system user. Undeclared: unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
QRun-IO/.github#2 adds a tag-and-release job that signs vX with the
QRUN_TAG_SIGNING_KEY secret after Maven Central confirms the artifact.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Tables, processes, app, possible values, join and widget carry the source
qbit name so hosts can tell them from their own; each table has its own nav
icon; the release items list widget has a label help entry.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Hosts that require referential integrity (kof22's foreign key guardrail) get
fk_release_notes_item_release_id from the qbit itself (ON DELETE CASCADE).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Producer VERSION constants lag the published RCs, so compare the versions
Maven recorded in each qbit jar (falling back to the producer's) and include
qqq-backend-core.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Standard release_notes_ tables with a Liquibase changelog (no foreign
keys) and seeded settings; once-per-version detection guarded by a unique
app + version key; GitHub and platform-component sources behind a
ReleaseSource SPI; a deterministic rule-based drafter and a sanitizer that
keeps internal references, personal data and secrets out of published
text; Publish, Skip and Redraft record actions and Check for new release;
one RELEASE notification per published release via QAlerts.notify; and the
release-notes UI API extension (releases, summary, seen) with a committed
OpenAPI contract and a complete help bundle.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>