Weave Code
Statamic Buddy Laravel Package
itiden/statamic-buddy
A companion addon for Statamic that bundles handy utilities to streamline everyday development and content workflows, helping site builders and developers get more done with less friction in the control panel.
Statamic addon to deploy frontend with Buddy
Frequently asked questions about Statamic Buddy
- What is itiden/statamic-buddy used for?
- It is a Statamic addon for deploying your frontend with Buddy, bundled with utilities that streamline everyday development and content workflows in the control panel. It installs as a Composer package into a Laravel-based Statamic application. Version 2.0.0 drops Statamic 3 support and targets newer Statamic majors.
- Does itiden/statamic-buddy support Statamic 3?
- No. The v2.0.0 release removes Statamic 3 support, so the current line targets Statamic 4 and later. Statamic 3 applications are effectively pinned to the package's 1.x line. Because the change is enforced as a Composer constraint, installs on Statamic 3 fail at resolution time rather than breaking at runtime.
- How do I install itiden/statamic-buddy with Composer?
- Run composer require itiden/statamic-buddy from the root of your Statamic application. Do this on a Statamic 4 or 5 host, since v2 will not resolve against statamic/cms ^3.0. Commit the updated composer.lock and deploy through your normal pipeline rather than editing vendor files.
- Which Statamic versions does itiden/statamic-buddy 2.x support?
- The v2.0.0 release note only states that Statamic 3 support was removed, so the package now targets Statamic 4 and above. Whether that means Statamic 4 only, Statamic 5 only, or both is not confirmed in the available note. Check the statamic/cms constraint in the package's composer.json before planning an upgrade.
- Why does composer require itiden/statamic-buddy fail on my Statamic 3 site?
- Version 2.0.0 drops Statamic 3 support, which surfaces as a Composer conflict against statamic/cms ^3.0. That is an install-time resolution failure, which is the desirable failure mode because nothing reaches production half-upgraded. Upgrade the host application's Statamic major first, then raise the constraint on this package.
- How do I migrate a Statamic 3 site so it can use this package again?
- Treat the package bump as the last step of a CMS upgrade, never the trigger for one. Move Statamic 3 to 4, then 4 to 5 if you need the current major, verifying PHP and Laravel minimums along the way. Only once the host resolves on Statamic 4 or 5 should you update itiden/statamic-buddy.
- Is the 1.x line of itiden/statamic-buddy still maintained or receiving security fixes?
- The available record contains no published EOL date and no security support statement for the 1.x line. Applications left on Statamic 3 are frozen on 1.x and should assume no further fixes, security patches, or compatibility work for future Laravel and PHP releases. Ask the maintainers directly if you need a formal support commitment.
- What PHP and Laravel versions do I need for itiden/statamic-buddy 2.x?
- The package notes do not state its own floors, but it inherits the requirements of its Statamic target. Statamic 4 and 5 raise the effective PHP and Laravel minimums, roughly PHP 8.1 and 8.2 respectively. Confirm your application's PHP and Laravel versions against the Statamic target before scheduling anything, since the Laravel upgrade is often the larger work item.
- What should I check in composer.lock before bumping itiden/statamic-buddy?
- Inventory every composer.lock in your estate for statamic/cms and itiden/statamic-buddy, and classify each app as already on Statamic 4 or 5, still on 3, or not using the package. Also confirm no other installed package pins statamic/cms to ^3.0, which would create an unresolvable diamond. That audit decides whether this is a one-line constraint bump or a coordinated multi-package upgrade.
- Is itiden/statamic-buddy 2.0.0 safe to roll out to production without other changes?
- The release note documents only the removal of Statamic 3 support, and a major bump justified solely by a support drop usually implies no runtime changes. However, the note does not guarantee that, so review the composer.json diff and CHANGELOG for refactors, tag or fieldtype output changes, and altered config defaults. Test in staging on a Statamic 4 or 5 copy of the site before promoting to production.
Weaver
How can I help you explore Laravel packages today?