Skip to content

Release v0.1.13 - #40

Open
roncodes wants to merge 4 commits into
mainfrom
release/v0.1.13
Open

roncodes wants to merge 4 commits into
mainfrom
release/v0.1.13

Conversation

@roncodes

@roncodes roncodes commented Oct 3, 2026

Copy link
Copy Markdown
Member

Release branch for v0.1.13, cut from main.

This branch collects #39: resource view registries, so extensions can add columns, actions and buttons to this engine's tables and details views.

Before merging

It depends on fleetbase/ember-core v0.3.25 (fleetbase/ember-core#96) and fleetbase/ember-ui v0.4.5 (fleetbase/ember-ui#187). Once both are published:

  1. Bump @fleetbase/ember-core to ^0.3.25 and @fleetbase/ember-ui to ^0.4.5 in package.json.
  2. Refresh pnpm-lock.yaml.

Merging this tags v0.1.13. The version comes from the branch name and is checked against the version files and the first line of RELEASE.md.

Extensions can add columns, row actions, bulk actions and toolbar buttons
through iam:table:<resource>:<slot>, and buttons and menu items to the edit
dialogs through iam:details:<resource>:<slot>.

- groups, roles and policies move to Layout::Resource::Tabular with
  actionButtons/bulkActions getters (roles and policies keep their reload)
- users keeps its TabularActions header; its columns merge in the controller
- edit dialogs pass registered details buttons as footer actionButtons
- stable ids on built-in items, query params include registered filters
- fix the delete-group accept button reading the misspelt aim.* key

Requires @fleetbase/ember-core 0.3.25 and @fleetbase/ember-ui 0.4.5.
feat: resource view registries for IAM tables
…surface>:<slot>

Follows ember-core 0.3.25: tables take @registry="<extension>:<resource>:table"
and details views @registry="<extension>:<resource>:details", e.g.
fleet-ops:driver:table:columns. Legacy component and tab registries are unchanged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant