Changelog
All notable changes to filament-relation-navigator are documented here.
Unreleased
1.4.1 - 2026-11-14
No code changes: documentation, AI tooling and repository hygiene.
Added
- Laravel Boost skill
relation-navigator-development(resources/boost/skills/), next to the guidelines: workflows for relation pages, the menu, options, headers, presets and testing. The guidelines tell agents to use it.
Documentation
- A documentation site with search: wit3.github.io/filament-relation-navigator. It is built from the README, the changelog and the config file, so it always matches them.
composer.jsonpointshomepageandsupport.docsto it. - The documentation is published for AI agents too: llms.txt, llms-full.txt and a Markdown version of every page.
Internal
- GitHub Actions pinned to commit SHAs; Dependabot with a 7-day cooldown, now also for the npm dependencies of the browser tests and of the documentation site.
AGENTS.md(andCLAUDE.md) for contributors working with AI agents.
1.4.0 - 2026-11-14
Every feature can now be turned on or off globally, per resource and per page or relation manager.
Added
- Options per resource: every option of the menu is read from the page, then from a static method with the same name on the resource, then from the config. For example
public static function hasRelationNavigatorRecordNavigation(): boolon a resource turns previous/next on for all its pages. Methods:getRelationNavigatorPreset(),isRelationNavigatorSearchable(),hasRelationNavigatorBadges(),hasDeferredRelationNavigatorBadges(),getRelationNavigatorShortcut(),hasRelationNavigatorMobileMenu(),hasRelationNavigatorRecordNavigation(),shouldRedirectRelationNavigatorTabs(). - "Open as page" per resource and per relation manager:
hasRelationPageLinks()on a resource,hasRelationPageLink()(or$hasRelationPageLinkwithInteractsWithRelationPage) on a relation manager, on top of the configrelation_manager_link. - Laravel Boost guidelines (
resources/boost/guidelines/core.blade.php): pick the package inboost:installand AI agents learn the traits and options. RelationNavigator::addRelationPageAction(),hasRelationPageAction()and theRELATION_PAGE_ACTIONconstant.
Changed
- "Open as page" is now an action in the header of the relation manager's table, next to its title and before its own actions, with an arrow icon. In 1.3.0 it was a link above the table, with an icon that looked like "full screen".
Deprecated
RelationNavigator::renderRelationManagerLink()and therelation-manager-linkview: the package no longer uses them. They still render the 1.3.0 link, for a render hook of your own, and will be removed in 2.0.
1.3.0 - 2026-11-14
A security fix, new features behind config switches, and a new default look for the menu. Update now if you use policies on your records. No breaking changes: every new key has a default in the code, so a published config from 1.2 keeps working.
Security
- Relation pages did not apply the record's
viewpolicy (1.0.0 to 1.2.1, GHSA-v3mh-w7qp-37gc). Filament checks it when the view page mounts, not incanAccess(), and relation pages only calledcanAccess(): a user deniedviewon a record, but allowedviewAny, could open its relation pages and see the related records and the header. Relation pages now run the same record check as the page they stand for (viewfor a view page,updatefor an edit page), also on every Livewire request.
Added
Links to relation manager tabs open the relation page (config
redirect_relation_tabs, defaultfalse):/customers/1?relation=billson the view or edit page redirects to/customers/1/bills, withwire:navigatein SPA mode. Tabs without a relation page, or that the record cannot see, stay where they are. Per page:shouldRedirectRelationNavigatorTabs()andgetRelationNavigatorTabRedirectUrl().Deferred badges:
menu.badgesalso takes'lazy'. The page then renders without the badge queries, and the menu loads the badges when it opens (one request, a spinner meanwhile). New page methodshasDeferredRelationNavigatorBadges()andgetRelationNavigatorBadges(), and$hasDeferredBadgesfor preset views. If you published the package views, updatemenu/partials/list.blade.phpbefore turning it on, or the menu shows no badges.Previous and next record buttons before the header actions of the pages with the menu (config
record_navigation, defaultfalse). They open the neighbour by key on the same page (view, edit, a relation page), or on its first page in the menu when it cannot open that one, and are disabled at the ends. They use the resource's own query, so tenancy and your scopes apply. Per page:hasRelationNavigatorRecordNavigation(),getRelationNavigatorRecordNavigationQuery(),getRelationNavigatorRecordNeighbours(). Nested resources are not supported yet: they show no buttons."Open as page" link above the table of every relation manager that has its own page, on the view and edit pages (config
relation_manager_link, defaulttrue). It links to the relation group's page for a manager inside a group, and tells apart two entries of the same manager (PostsRelationManager::make([...])) by their properties.RelationNavigator::getRelationManagerPageUrl()returns the same URL for your own buttons.RelationPage::canAccessRecord()andRelationNavigator::canAccessRecordPage(): the record check of the view and edit pages.
Fixed
- The menu lists the view and edit pages only when the user can open them for the record (
viewandupdatepolicies): a user who cannot edit a record no longer sees an Edit item that ends in a 403.
Changed
- The default menu is now the
githubpreset with the search field (menu.preset=github,menu.searchable=true): it is the one with the most features. Apps that published the config keep what they set. To keep the menu of 1.2 and earlier, set'preset' => 'simple'and'searchable' => falseinconfig/filament-relation-navigator.php, or overridegetRelationNavigatorPreset()andisRelationNavigatorSearchable()on the page.
Internal
- Tests for each feature, tenancy, nested resources and record policies included, and a browser test for the deferred badges. README with a GIF and new screenshots.
1.2.1 - 2026-11-14
Bug fixes and tests. No API changes.
Fixed
- Resources registered through a configuration (
UserResource::make('admins')) had no generated relation pages: they now get them under the configuration's slug, with its middleware, as Filament does for the resource's own pages. - On a read-only storage (read-only containers, serverless) the generated page classes go to the system temporary directory. If no directory is writable, the error says how to choose one.
- With a
modshortcut,aria-keyshortcutsdeclares both variants (Meta+…andControl+…) instead of onlyMeta. - While searching, the separator line no longer shows on top of the list when the block above it is filtered out.
Internal
- Tests with cached routes, configured resources and
RelationManager::make([...])entries. - CI: a job on the lowest allowed versions (Filament 4.13, Laravel 12, Livewire 3.8), browser tests on Filament 4 too, releases published from the changelog when a tag is pushed, Dependabot for the GitHub Actions.
1.2.0 - 2026-11-14
Added
- Tooltip on the button that opens the menu: the heading and the shortcut keys, shown as ⌥ ⇧ R on a Mac and Alt Shift R elsewhere.
- Shortcut that opens the menu from anywhere on the page with the search field ready, like GitHub's repository switcher. Config
menu.shortcut(defaultalt+shift+r,nullturns it off), orgetRelationNavigatorShortcut()per page. It matches the physical key (any keyboard layout, Option on a Mac), does nothing while typing in a field, opens only the visible menu, and is never registered when it equals one of the panel's global search shortcuts. RelationNavigator::getShortcutKeys(),getShortcutCondition()andclashesWithFilament();$shortcutand$shortcutKeysfor preset views, and themenu.partials.trigger-attributespartial for buttons of your own.
Changed
- The caret of the
githubpreset has a light background, lighter on hover, as on GitHub. Runphp artisan filament:assetsafter updating. HasRelationNavigatordeclaresgetRecord()andhasRecord()as abstract. Record pages already have them, so nothing changes for them. A page using the trait without a record, which already failed when rendered since 1.0.1, now fails when its class is loaded, with a clear PHP error; because the menu loads the record pages of the resource, this also breaks the other record pages of that resource until the trait is removed from that page.
1.1.0 - 2026-11-14
New features, all backwards compatible.
Added
- Small screens: Filament hides the breadcrumbs below 40rem; there the menu now shows above the page heading, on the pages that use
HasRelationNavigator. Configmenu.mobile(defaulttrue), orhasRelationNavigatorMobileMenu()per page. Its few style rules are inline, so it works even iffilament:assetswas not run after the update. - Keyboard navigation in the menu: Down from the search field enters the list, Up and Down move between the pages, Up from the first one goes back to the search field.
- Separator between the record pages and the relation pages. Config
menu.separator(defaulttrue). RelationNavigatorItem::isRelationPage(), and$hasSeparatorfor preset views.- Translations: Spanish, German, French, Brazilian Portuguese and Dutch.
Changed
- The menu looks slightly different with the separator on (a line between the two blocks). Set
menu.separatortofalseto keep the 1.0 look. - Run
php artisan filament:assetsafter updating to get the separator line.
1.0.1 - 2026-11-14
Bug fixes and tests. No API changes.
Fixed
- With a relation page class you wrote, a relation whose URL equals one of the resource's own pages (for example
relationRoutes()spread after'timeline' => ...::route('/{record}/timeline')) replaced that page. The resource's page now always wins and that relation has no page. Generated relation pages were not affected. - Relation managers' badges are computed once per request, even when the breadcrumb menu and the record sub-navigation both show them.
- A menu preset pointing to a missing view now says which config option to check, instead of a generic "View not found".
Changed
HasRelationNavigatorassumes the page has a record, as documented. On a page without a record it did nothing before; now it fails like any other record method.
Internal
- Tests for nested resources, clusters, tenancy and SPA mode, and browser tests for the searchable menu.
- PHPStan (Larastan) at level 8 in CI.
1.0.0 - 2026-11-14
First public release.
- Every relation manager of a resource can have its own page at
/{record}/{slug}, rendering the relation manager you already have: same table, actions, badges and authorization. - Opt in with
HasRelationPageson the resource orInteractsWithRelationPageon a relation manager. No page class to write: the routes join the resource's own route group and the page class is generated on demand. Works withroute:cache. - Optional page class of your own (
make:filament-relation-navigator) to customise the relation pages. - Header above the relation (
relationPageHeader()), header actions and header/footer widgets, from the resource or the relation manager. - Breadcrumb menu with the record pages that use
HasRelationNavigatorand every relation page the user can see. - Menu presets
simpleandgithub, optional search, badges, presets of your own (make:filament-relation-navigator-preset) and publishable views. - Native record sub-navigation from the same items.
- English and Italian translations.
- Filament 4 and 5, Laravel 12 and 13, PHP 8.2 to 8.5.