Docs / LocalBoost AI

Changelogs

Review version history, release notes, update instructions, database changes, addon updates, and compatibility notes.

Estimated reading: 4 minutes

Changelogs

The Changelogs page helps buyers and administrators understand what changed between LocalBoost AI releases. Read this page before every production update so you know which files, database tables, modules, permissions, routes, and customer-facing workflows may be affected.

What Changelogs Are Used For

  • Review new features added to LocalBoost AI.
  • Review bug fixes, compatibility changes, and behavior updates.
  • Check security improvements and recommended upgrade urgency.
  • Check database migrations and table changes before updating production.
  • Review addon compatibility for CRM, Google Business, automation, loyalty, and future marketplace modules.
  • Identify changes that may affect businesses, growth tools, coupons, booking pages, feedback forms, reports, AI tools, assets, plans, or admin settings.

Recommended Release Note Format

Each release should use a consistent format so buyers can quickly decide whether they need to update immediately and what they should test after updating.

  • Version: release number, for example 1.0.1.
  • Release date: date the update was published.
  • Type: major, minor, patch, security, or addon update.
  • Summary: short explanation of the release.
  • New features: features added in this version.
  • Improvements: UX, performance, workflow, or admin improvements.
  • Bug fixes: issues resolved in this version.
  • Database changes: migrations, new tables, changed columns, or seed updates.
  • Breaking changes: changes that may affect custom edits or integrations.
  • Post-update checks: workflows buyers should test after upgrade.

Example Changelog Entry

Version 1.0.1 - Patch Update

  • Summary: improves dashboard visibility, marketplace addon handling, and business workflow documentation.
  • New: added expanded documentation for admin workspace, marketplace, installation, upgrades, and changelogs.
  • Improved: refined reporting, CRM, automation, and Google Business addon guidance.
  • Fixed: corrected addon sidebar visibility when modules are removed or disabled.
  • Database: includes migration updates for optional addon modules where applicable.
  • Post-update: clear cache, run migrations, then test businesses, growth tools, CRM, reports, AI tools, automation, marketplace, and admin settings.

How Buyers Should Read Changelogs

  1. Check whether the update is for the main LocalBoost AI product or an addon module.
  2. Read the summary to understand the release purpose.
  3. Review database changes before running migrations.
  4. Review breaking changes before replacing files on a customized installation.
  5. Back up the database, application files, .env, and storage folder.
  6. Update the main LocalBoost AI product before addon packages.
  7. Run migrations and clear application cache.
  8. Test the workflows listed in the post-update checklist.

Update Testing Checklist

  • Admin login and dashboard load correctly.
  • User workspace and business dashboard load correctly.
  • Business profiles, customers, feedback forms, lead forms, coupons, booking pages, and QR assets still work.
  • Review Booster, AI Review Reply, Campaign Builder, and Content Writer load correctly when enabled.
  • Reports and analytics pages show current data.
  • Files, landing pages, QR codes, and public pages open correctly.
  • Plans, billing, subscriptions, credits, and payment history remain accurate.
  • Marketplace packages show the correct installed version.
  • Optional addons are hidden when removed and visible when installed.
  • Google Business, CRM, automation, and other addon routes work only when their modules are installed.

Addon Changelog Notes

Optional modules should have their own changelog notes when they change independently from the main product. This is especially important for marketplace packages that can be installed, updated, disabled, or removed separately.

  • CRM Addon: document changes to customers, segments, tags, tasks, automations, and CRM reports.
  • Google Business Addon: document changes to location sync, profile data, reviews, AI replies, and integration settings.
  • Automation Addon: document changes to email, WhatsApp, webhook, coupon, booking, review, and lead automation flows.
  • Loyalty or referral addons: document changes to rewards, stamps, referrals, redemptions, and campaign limits.

Important Notes

  • Always back up before applying updates.
  • Do not skip database migrations unless the release note explicitly says no migration is required.
  • Do not update addon modules before the main product when the changelog says the addon depends on a newer core version.
  • Custom edits may be overwritten during updates.
  • After updating, clear cache and test the public site, admin workspace, user workspace, public QR pages, booking pages, coupon pages, feedback forms, and reports.

Troubleshooting After an Update

A page returns 404 after update
Clear route cache and confirm the module provider is loaded.

A menu item is missing
Confirm the related module exists, the provider is registered, the plan permission is enabled, and cache has been cleared.

Database error appears
Run migrations and check whether the update contains required schema changes.

Old design or text still appears
Clear view cache, browser cache, and any public documentation cache.