What's Changed

Supply-chain and packaging hygiene. No application API or behavior changes.

Security & CI

• Added a security policy for private vulnerability reports
• Enabled Dependabot updates for GitHub Actions, with a short cooldown before new releases are proposed
• Pinned CI Actions to immutable commit SHAs

Packaging

• Kept AI assistant files and the security policy out of the Composer dist archive

Full Changelog: https://github.com/inerba/filament-db-config/compare/v1.3.4...v1.3.5

This release removes the need for a custom Blade view by providing a built‑in default view, which can still be overridden when needed. This simplifies the setup and eliminates an unnecessary stub.

Full Changelog: https://github.com/inerba/filament-db-config/compare/v1.3.3...v1.3.4

Improved the Blade template to support modals within widgets.

Full Changelog: https://github.com/inerba/filament-db-config/compare/v1.3.2...v1.3.3

HELLO AI: Added optional Laravel Boost Skill for filament-db-config

• https://agentskills.io/what-are-skills
• https://laravel.com/ai/boost

Full Changelog: https://github.com/inerba/filament-db-config/compare/v1.3.1...v1.3.2

What's New

Safe Configuration Helper

Added safe_db_config() - a fault-tolerant wrapper for accessing database configuration values with built-in exception handling.

Key Features:

• Graceful Error Handling: Catches all exceptions (database connection errors, missing tables, serialization issues) and returns the default value instead of crashing
• Perfect for Critical Paths: Use it in service providers, middleware, bootstrapping phases, or anywhere database availability isn't guaranteed
• Zero Breaking Changes: New helper function that complements the existing db_config()

Usage Example:

// Returns 'Default Name' if database is unavailable or any error occurs
safe_db_config('website.site_name', 'Default Name');

When to Use:

• ✅ Service providers that run before database initialization
• ✅ Middleware or early application lifecycle hooks
• ✅ Development/CI environments with unreliable database access
• ✅ Migration or maintenance scenarios
• ✅ Any critical path where configuration failure shouldn't interrupt the app

🔧 Technical Details

• Full backward compatibility maintained
• No breaking changes
• Follows existing package conventions and coding standards

Added support for Filament v5 while keeping full compatibility with Filament v4.

Changes:

composer.json: "filament/filament": "^4.0" → "filament/filament": "^4.0|^5.0" Upgrade:

composer require inerba/filament-db-config:"^1.3" If you move your app to Filament v5, also upgrade Livewire to v4. That's it.

This release adds support for creating widgets with database-backed configurations. The new structure enables centralized and localized management of widget settings, making dashboards and modules in FilamentPHP more modular and easier to organize.

Support for database-configurable widgets

Introduced a centralized structure for widget settings management, based on DbConfigTrait and the new abstract class AbstractWidgetSettings.

Improved localization

Added “Last updated” message in IT, EN, FR, ES, with automatic date formatting according to the user's language.

Full Changelog: https://github.com/inerba/filament-db-config/compare/v1.1.7...v1.2.0

🔧 Technical Improvements

• Command Handling: Fixed duplication issue with the Settings suffix in DbConfigCommand.
• Test Coverage: Introduced DbConfigCommandSettingsSuffixTest.php to ensure correct suffix handling.

📖 Documentation & Visuals

• Animated demo GIF replaces static screenshot.
• Enhanced code samples with syntax highlighting, better formatting, and clearer notes.

🔗 Full Changelog: https://github.com/inerba/filament-db-config/compare/v1.1.6...v1.1.7

Unified form handling with $form, safer JSON upsert & caching in DbConfig, last-updated helpers, global helper, and quality tooling.

🚀 Added

• AbstractPageSettings
  • Support for using $form (with $content as fallback) for filling and reading state.
  • lastUpdatedAt() helper to get a formatted “last updated” timestamp for the settings group.
  • Save action now includes a mod+s keyboard shortcut.
• DbConfig
  • Caching support (namespaced cache keys) and safer JSON handling with exceptions.
  • getGroupLastUpdatedAt() to retrieve a formatted last-updated timestamp for a group.
• Global helper
  • db_config() for quick access to stored settings.
• i18n
  • New Spanish and French language files.

✨ Changed

• AbstractPageSettings: removed the hard dependency on InteractsWithSchemas; state is read via $form->getState() when available (falls back to $content).
• stubs/page.stub: default method is now form() (the old content() continues to work).
• Expanded PHPDocs and inline comments across AbstractPageSettings and DbConfig.
• declare(strict_types=1); added to new/updated PHP files.

🐛 Fixed

• More robust save flow: throws a clear RuntimeException if the form instance does not expose getState().

🛠 Dev

• Added phpstan/phpstan to require-dev.
• Minor composer tidy-ups and docs cleanup.

Upgrade notes

• No breaking changes.
• Consider implementing form(Schema $schema) in old pages; legacy content() remains supported.
• You can now display “last updated” using AbstractPageSettings::lastUpdatedAt() or DbConfig::getGroupLastUpdatedAt().

Full Changelog: https://github.com/inerba/filament-db-config/compare/v1.1.5...v1.1.6

This version includes minor bug fixes and stability improvements. Full Changelog: https://github.com/inerba/filament-db-config/compare/v1.1.4...v1.1.5

This release introduces a new feature for setting default values on settings pages and includes improvements to the package's testing infrastructure.

✨ Added

• Default Data for Settings Pages: A getDefaultData() method can now be defined in settings page classes to provide default values for the form. Values stored in the database will override these defaults.

🚀 Improved

• Scaffolding Stub: The artisan make command for settings pages now includes the getDefaultData() method in the generated file.

• Testing Infrastructure: The test environment has been updated to ensure reliable testing of Filament and Livewire components. This includes automatic database migrations, registration of all required service providers, and proper session initialization.

Full Changelog: https://github.com/inerba/filament-db-config/compare/v1.1.3...v1.1.4

This release marks a step forward for filament-db-config, introducing greater flexibility, robustness, and reliability. The package is now more configurable than ever and is backed by a full test suite to ensure the highest quality.

🚀 New Features

• Package Configuration: You can now customize the package's behavior by publishing the config/db-config.php configuration file.
• Custom Table Name: You can specify a custom name for the settings table via the table_name option in the configuration file.
• Flexible Cache Control: The cache management has been enhanced. You can now:
  • Set a custom prefix for all cache keys (cache.prefix).
  • Define a cache lifetime (TTL) in minutes (cache.ttl), allowing for temporary caching instead of only permanent.

✨ Improvements

• Complete Test Suite: The package now includes a full test suite written in Pest, covering all core features and the new configuration options.
• Continuous Integration (CI): A GitHub Actions workflow has been implemented to automatically run tests on every push and pull request, ensuring code stability.
• Documentation Overhaul: The README.md file has been rewritten to be clearer and more comprehensive, with detailed sections on installation, configuration, and testing.

⚙️ Internal Changes

• The internal logic has been updated to cleanly and efficiently integrate the new configuration options.
• Unused Model and Factory files have been removed to make the package lighter and more consistent.

Full Changelog: https://github.com/inerba/filament-db-config/compare/v1.1.2...v1.1.3

Full Changelog: https://github.com/inerba/filament-db-config/compare/v1.1.1...v1.1.2

Add CanOpenUrlInBrowser trait to DbConfigCommand

What's Changed in v1.1.0 🚀 New Features Interactive prompts: Added interactive command prompts to improve command usability and user experience Enhanced command interface: Commands are now more user-friendly with better guidance and input validation 📚 Documentation Improved README: Updated README.md with better plugin description and clearer documentation Spatie Settings comparison: Added detailed explanation of differences compared to Spatie Settings package to help users understand when to use this plugin 🔧 CI/CD Improvements Code quality: Added GitHub Actions workflow for automated code style checks Better maintenance: Automated code style validation ensures consistent code quality across contributions

Full Changelog: https://github.com/inerba/filament-db-config/compare/v1.0.1...v1.1.0

Full Changelog: https://github.com/inerba/filament-db-config/compare/v1.0.0...v1.0.1

This is the first stable release of DB Config, a Filament plugin that provides a simple, database-backed key/value store for application settings.

It offers:

• Full support for Laravel 12 and Filament 4.
• A clean API to read and write values with transparent caching.
• Seamless integration with Filament, including an Artisan generator to scaffold settings pages.
• No custom Eloquent models required: values are persisted as JSON in a dedicated table.

Use this package to manage settings, frontend semi-static pages, various info and more...