- How do I install anselmokossa/filament-changelog in a Laravel app?
- Install it with Composer using composer require anselmokossa/filament-changelog, then register the plugin in your Filament panel provider's plugin() method. The package ships migrations, so run php artisan migrate afterwards and publish the config if you need to change the changelog file path or locale. Because it targets Filament v5, confirm your panel already runs that major version before installing.
- Does filament-changelog support Filament v3 or v4?
- No, the package is built for Filament v5, so panels still on v3 or v4 should not expect it to work. Small plugins with a single maintainer rarely keep parallel branches for multiple Filament majors. Read the composer.json constraints in the repository and test it in a sandbox rather than assuming compatibility with any other Filament or Laravel version.
- Is the database or the CHANGELOG.md file the source of truth in this package?
- The package is deliberately hybrid: it stores structured changelog records in a database table and also reads and writes a Keep a Changelog style CHANGELOG.md file. The documentation does not state plainly which side wins on conflict, so verify this before depending on it. Decide deliberately whether the database is canonical and the file a generated artifact, or the file is canonical and the database an index, and enforce that direction in your workflow.
- Can I import my existing CHANGELOG.md into filament-changelog?
- Yes, importing is one of the advertised features, and the package can parse an existing Keep a Changelog file into records you can browse in the Filament reader page. Import is best-effort against the Keep a Changelog structure, so unusual headings or hand-rolled formats may need cleanup afterwards. Test the import against a copy of your real changelog before running it against production data.
- Where does filament-changelog write the CHANGELOG.md file?
- By default it works with a CHANGELOG.md in the project root, and the path should be overridable in the published config file. That means your application needs write permission to that location at runtime, which fails on read-only container filesystems or ephemeral deployments. Confirm the path setting and whether the write is atomic before enabling changelog editing in production.
- How do I restrict who can edit changelogs in the Filament panel?
- The package is described as Shield-ready, so it can be wired into Filament Shield permissions or your own policies instead of being open to every panel user. Gate the changelog resource so viewing is separate from creating, editing, and deleting entries. Check how the authorization hooks are exposed, because edit access here also means write access to a file in your repository.
- Does filament-changelog support multiple languages?
- It ships with English and Portuguese translations for the plugin's UI strings, which covers the reader page and admin screens. Additional locales can normally be added by publishing and overriding the package translation files. Per-entry multilingual changelog content is not part of the package and would be content modelling you add yourself.
- Can I create changelog entries from code with a fluent API instead of the admin UI?
- Yes, the package advertises a fluent API, so you can create or update releases programmatically from seeders, console commands, or deploy scripts. That is useful when release notes should be generated by your pipeline rather than typed into the panel. Check the README for the exact methods and the version format it expects.
- How do I test that filament-changelog works correctly in my application?
- There is no published CI matrix, so verify it in a throwaway Laravel plus Filament v5 app: install, migrate, import a sample Keep a Changelog file, and edit an entry through the panel. In your own suite, use Livewire testing helpers to assert the reader page renders and that imports produce the expected records. Point the config at a temporary file path so tests never mutate your real repository CHANGELOG.md.
- Is anselmokossa/filament-changelog production ready, and what are the alternatives?
- It is a small, single-maintainer package with very few stars and no dependents, so there is no adoption history or security response process to rely on. Before adopting it, confirm the canonical repository, since the Composer vendor name and the GitHub owner in the links do not match. For a critical need, a simple Eloquent model with a Filament resource, or a static CHANGELOG.md rendered in your app, gives you the same result with no third-party dependency.