paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 43 Packages Projects Releases Wiki Activity

delete changesets

Browse Source 
Signed-off-by: aramissennyeydd <aramis.sennyey@doordash.com>
This commit is contained in:
aramissennyeydd
2026-03-11 10:04:49 -04:00
committed by Patrik Oldsberg
parent 10f8fa1df8
commit 0ed572576e
3 changed files with 0 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.changeset/ff-perm-enabled-frontend-app-api.md
-7
View File
@@ -1,7 +0,0 @@
---
'@backstage/frontend-app-api': patch
---
Extensions with an `enabled` predicate are now evaluated before app tree instantiation, so pages that do not meet their conditions are excluded from the router tree.
`prepareSpecializedApp().finalize()` is now async. Extensions whose `enabled` predicate references `permissions` are checked against the current user's allowed permissions (via a single batched call to `permissionApiRef`) before the app tree is instantiated.
.changeset/ff-perm-enabled-frontend-defaults.md
-5
View File
@@ -1,5 +0,0 @@
---
'@backstage/frontend-defaults': patch
---
Updated `createApp` to await the now-async `finalize()` call from `prepareSpecializedApp`, enabling permission-gated extensions to be resolved before the app tree is rendered.
.changeset/ff-perm-enabled-frontend-plugin-api.md
-7
View File
@@ -1,7 +0,0 @@
---
'@backstage/frontend-plugin-api': patch
---
Added `enabled` option to `createExtension`, `createExtensionBlueprint`, and `AppNodeSpec`, accepting a `FilterPredicate` from `@backstage/filter-predicates` to conditionally enable extensions based on feature flags or other runtime conditions.
Added `permissions` option to `createFrontendPlugin` and `createFrontendModule`, allowing plugins and modules to declare which permissions they use. These permissions are checked at app startup so that extensions can conditionally enable themselves using a `permissions` predicate, e.g. `enabled: { permissions: { $contains: 'catalog.entity.create' } }`.