- What is chrisreedio/bastion used for in Laravel?
- Bastion is an opinionated SSO user role management package for Laravel. It provides a secure, extensible foundation for authentication and access control, with clean configuration and sensible defaults. It is especially relevant for Laravel applications that use Filament admin panels.
- Does Bastion v4.1.0 require Filament v4?
- Yes, the v4.1.0 release explicitly targets Filament v4 compatibility. Teams still on Filament v3 cannot adopt Bastion v4.1.0 without first upgrading Filament, which is a major platform change. Confirm the package composer constraints before planning the upgrade.
- How do I install Bastion in a Laravel application?
- Install the package with Composer using chrisreedio/bastion, then follow the repository README for any required configuration publishing and migrations. Because v4.1.0 targets Filament v4, verify your Filament and Laravel versions first. Test the install in a staging environment before rolling it out to production.
- What Laravel and PHP versions does Bastion v4.1.0 support?
- The provided release notes do not list exact Laravel and PHP constraints, but Filament v4 likely requires Laravel 11+ and PHP 8.2+. You should confirm the actual composer.json constraints in the Bastion repository before upgrading. Do not assume compatibility with older Laravel or PHP versions.
- How does the bastion:sync command handle multiple Filament panels?
- Bastion v4.1.0 adds an optional panel argument to the bastion:sync command. That supports modern Filament multi-panel architectures where roles or access control need to be synced per panel. Verify whether the argument defaults to previous behavior or whether existing sync invocations must be updated.
- What are the breaking changes in Bastion v4.0.0?
- The provided information does not detail the v4.0.0 breaking changes, and the compare link starts at v3.0.1. Because v4.1.0 is a major version leap, treat it as a breaking upgrade and review the v4.0.0 release notes and changelog. Pay particular attention to the Filament v4 dependency and the Parent Resource Check compatibility fix.
- Can I use Bastion with Filament v3?
- Bastion v4.1.0 explicitly targets Filament v4, so it is not directly applicable to a Filament v3 application. You would need to upgrade Filament to v4 first, which is a substantial project. If you cannot upgrade Filament yet, stay on a compatible Bastion version or evaluate another approach.
- How do I test Bastion role and permission changes before production?
- Run regression tests on roles, permissions, and resource visibility after upgrading Bastion. Test bastion:sync both with and without the new panel argument to confirm backward compatibility. Also validate any custom resource checks or permission logic affected by the Parent Resource Check change.
- Is Bastion suitable for production multi-panel Filament admin applications?
- Bastion is a strong fit for Laravel teams already on Filament v4, and the panel argument improves support for multi-panel admin setups. The package itself is unlikely to be a performance bottleneck, but you should test permission-check complexity with large role sets. Plan for major-version upgrades and review release notes before production rollout.
- How actively is Bastion maintained and when should I consider alternatives?
- Bastion shows active maintenance through recent feature work and dependabot PRs, but it follows a single-maintainer pattern and has no commercial support indicated. Rely on GitHub issues, discussions, and the changelog, and budget time for source review during major upgrades. If you are not on Filament v4 or need vendor-backed support, evaluate alternatives before committing.