The GitHub Actions job "Backend CI" on hertzbeat.git/2.0.0 has failed.
Run started by GitHub user tomsun28 (triggered by tomsun28).

Head commit for run:
96322d047577270f3ab6bf5dcaf8fc1d76c8fad7 / tomsun28 <[email protected]>
fix(migration): make V200 upgrade path idempotent and realign contract tests

The 2.0 migration chain (B200 baseline + V200 upgrade) collided with the
master-era migration contract tests and contained real defects:

- mysql/postgresql V200 scripts ran bare CREATE/ALTER statements that fail
  on any database where the tables already exist; every statement is now
  safe to re-run, mirroring the h2 variant and the V190 convention. MySQL
  ALTERs move into an information_schema-guarded routine, and fingerprint /
  group_key are narrowed to ASCII so the workspace-scoped unique indexes
  fit the 3072 byte limit the B200 baseline pins.
- MigrationInventoryTest and AbstractMigrationUpgradeTest now describe the
  2.0 chain (released V190 -> current V200, B baseline scripts allowed);
  the schedule-owner seed replays the cleanup V190 already applied.
- GreptimeSignalInitializer gains @ConditionalOnNormalBusinessRuntime so
  the setup-gated runtime does not try to reach GreptimeDB, matching the
  other signal initializers.
- EntityFreeObservabilityTransitionContractTest follows the current
  self-telemetry signature and isolates SDK telemetry by Greptime
  database, and reads the React route constants from
  explore-signal-paths.ts where they now live.
- The embedded H2 baseline pins the refreshed SHA-256 of the shared
  MySQL baseline, and the assembly deployment copy explicitly disables
  the springdoc document switches.

Generated with [Devin](https://devin.ai)

Co-Authored-By: Devin 
<158243242+devin-ai-integration[bot]@users.noreply.github.com>

Report URL: https://github.com/apache/hertzbeat/actions/runs/38114936036

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to