james.maesandClaude Opus 5.5
c8f6f59505
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>
16 lines
721 B
Markdown
16 lines
721 B
Markdown
# Upgrading QBit Release Notes
|
|
|
|
## First release
|
|
|
|
There is no previous release. See [README.md](README.md) for installation.
|
|
|
|
Use QQQ 4.1.0-RC.13 or newer and Java 21. Include
|
|
`db/liquibase/qbit-release-notes/release_notes.changelog.sql` once in the host's Liquibase changelog
|
|
and run migrations before the application starts; the qbit does not apply them. Seeding is
|
|
insert-only, so edited settings are kept.
|
|
|
|
Register the producer with the running release version, grant `release_notes.manage` and
|
|
`release_notes.publish`, and call `ReleaseNotesRuntime.of(qInstance).detectInBackground()` after the
|
|
server starts. The first release records its own GitHub release only (there is no previous version
|
|
to compare against).
|