chore: lock the plugin boundary and remove 2.9.0 leftovers

This commit is contained in:
LukeGus committed 2026-09-25 07:24:46 -05:00
1 parent 6489b62ece
commit 2961297989
399 files changed
+3964 -5627

No files matched your search

+10 -1
View File
@@ -38,7 +38,16 @@
"descriptionKey": "permissions.use.description",
"defaultRoles": ["admin", "user"]
}
]
],
"http": {
"legacyRedirects": [
{
"from": "/termix-id/u",
"to": "/u",
"status": 308
}
]
}
},
"locales": "locales",
"platforms": ["linux", "win32", "darwin"]
+1 -1
View File
@@ -6,7 +6,7 @@
"scripts": {
"build": "termix-plugin build",
"test": "termix-plugin test",
"typecheck": "tsc -b ../../tsconfig.plugins.json ../../tsconfig.plugins.frontend.json",
"typecheck": "tsc -b ../../tsconfig.plugins.backend.json ../../tsconfig.plugins.frontend.json",
"validate": "termix-plugin validate"
},
"devDependencies": {
@@ -0,0 +1,20 @@
import { describe, expect, it } from "vitest";
import { validateManifest } from "@termix/plugin-sdk/manifest";
import manifest from "../../manifest.json";
// Old URLs something outside Termix still calls keep reaching the plugin.
const redirects = manifest.contributes.http.legacyRedirects as unknown[];
describe("legacy URLs", () => {
it("declares them in a manifest that validates", () => {
expect(validateManifest(manifest)).toEqual([]);
});
it("redirects /termix-id/u, which servers provisioned with a 2.8 Termix ID resolver URL fetch", () => {
expect(redirects).toContainEqual({
from: "/termix-id/u",
to: "/u",
status: 308,
});
});
});