Fix CI: test manifests need tools/pipes/hooks for extension type
All checks were successful
CI/CD / detect-changes (pull_request) Successful in 4s
CI/CD / test-frontend (pull_request) Successful in 6s
CI/CD / test-sqlite (pull_request) Successful in 2m46s
CI/CD / test-go-pg (pull_request) Successful in 2m47s
CI/CD / build-and-deploy (pull_request) Successful in 1m21s

ValidateManifest() now enforces type-specific constraints on bundled
install too. Two tests used type "extension" without any tools/pipes/hooks,
which is correctly rejected. Added hooks field to make them valid.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-03-31 17:36:14 +00:00
parent 77ef5b43d9
commit f4e66afc80
2 changed files with 2 additions and 0 deletions

View File

@@ -171,6 +171,7 @@ func TestBundledInstall_DormantPackage(t *testing.T) {
"id": "dormant-pkg",
"title": "Dormant Package",
"type": "extension",
"hooks": []string{"on_install"},
"requires": []string{"chat"},
})

View File

@@ -451,6 +451,7 @@ func TestUpgrade_PackageDormantOnUnmetRequires(t *testing.T) {
"title": "Future",
"type": "extension",
"version": "1.0.0",
"hooks": []string{"on_install"},
"requires": []string{"kernel>=99.0.0"},
})