test(api): pin /version schema assertion to migration 63
The #[ignore]-gated version_includes_public_base_url pinned schema=42 but migrations accreted to 63 across the v1.2 template track (…0060–0063), so it failed under `--include-ignored`. Re-pin to current reality per the test's own intent. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -891,12 +891,12 @@ async fn version_includes_public_base_url(pool: PgPool) {
|
|||||||
assert!(v["public_base_url"].is_string());
|
assert!(v["public_base_url"].is_string());
|
||||||
assert_eq!(v["api"], 1);
|
assert_eq!(v["api"], 1);
|
||||||
// `schema` is migrations::latest_version() — the highest embedded
|
// `schema` is migrations::latest_version() — the highest embedded
|
||||||
// migration number. Bumped to 42 by audit 2026-06-11's
|
// migration number, currently 63 (…0060_group_suppressions ..
|
||||||
// 0042_secrets_envelope_version.sql (H-D1). Both this and `sdk` had
|
// 0063_materialized_unique from the v1.2 template track). This test is
|
||||||
// rotted (pinned at 6 / "1.1" while the codebase moved to 41 / "1.10")
|
// #[ignore]-gated so it doesn't run in the default `cargo test`; pinned to
|
||||||
// because the test is #[ignore]-gated; pinned to current reality so
|
// current reality so an unintended schema change is still caught. Bump it
|
||||||
// unintended changes are still caught.
|
// whenever a migration lands.
|
||||||
assert_eq!(v["schema"], 42);
|
assert_eq!(v["schema"], 63);
|
||||||
assert_eq!(v["sdk"], "1.10");
|
assert_eq!(v["sdk"], "1.10");
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user