frontend-plugin-api: make pluginId optional in FrontendFeature type

Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>

.changeset/fix-frontend-feature-compat.md

@@ -0,0 +1,5 @@
+---
+'@backstage/frontend-plugin-api': patch
+---
+
+Made the `pluginId` property optional in the `FrontendFeature` type, allowing plugins published against older versions of the framework to be used without type errors.

.patches/pr-32905.txt

@@ -0,0 +1 @@
+Fix type compatibility for older plugins in FrontendFeature type

packages/frontend-plugin-api/report.api.md

@@ -1336,7 +1336,11 @@ export type FetchApi = {
 export const fetchApiRef: ApiRef<FetchApi>;
 
 // @public (undocumented)
-export type FrontendFeature = FrontendPlugin | FrontendModule;
+export type FrontendFeature =
+  | (Omit<FrontendPlugin, 'pluginId'> & {
+      pluginId?: string;
+    })
+  | FrontendModule;
 
 // @public (undocumented)
 export interface FrontendFeatureLoader {

packages/frontend-plugin-api/src/wiring/types.ts

@@ -73,4 +73,6 @@ export type ExtensionFactoryMiddleware = (
 ) => Iterable<ExtensionDataValue<any, any>>;
 
 /** @public  */
-export type FrontendFeature = FrontendPlugin | FrontendModule;
+export type FrontendFeature =
+  | (Omit<FrontendPlugin, 'pluginId'> & { pluginId?: string })
+  | FrontendModule;