Changelogs

Changelogs help buyers understand what changed, what to test, and whether addon or configuration work is required after an update. Read changelogs before updating production.

Version 1.0.0 - Initial Release

Added

User workspace for Dashboard, Capture, Leads, AI Studio, Automation, Publish, Reports, Assets, Account, and Help.
Capture modules for Create Wizard, Forms, Form Builder, Funnels, Multi-step Funnels, Signals, Templates, and Conversion Pages.
Lead modules for Responses, All Leads, Pipeline, Segments, Tags, Activities, lifecycle stages, source metadata, and lead scoring.
Publishing modules for Share Links, Embed Codes, QR Codes, Brand, Custom Domain, and Files.
Admin workspace for dashboard monitoring, AI center, users, teams, content operations, finance, settings, marketplace, localization, cache, crons, integrations, files, and system information.
Marketplace-ready package model for addons, updates, ZIP installation, purchase-code installation, rescans, and uninstall workflows.
Billing, plans, feature limits, AI credits, payment gateways, support, integrations, and SaaS permissions.

Improved

Documentation quality for installation, setup flow, module architecture, permissions, marketplace readiness, and buyer usability.
Setup guidance for forms, funnels, surveys, leads, QR tools, files, custom domains, reports, automations, integrations, and admin operations.
Permission explanations for workspace users, team members, admins, plans, and addons.

Fixed

Initial release cleanup for visibility handling, permission checks, addon safety, UI consistency, marketplace package behavior, and documentation corrections.
Safer guidance for cache clearing, package updates, team permission handling, route visibility, and feature availability when addons are missing.

Recommended Release Note Format

Use sections for Added, Improved, Fixed, Changed, Removed, Security, Upgrade Notes, Addon Notes, and Testing Checklist. Mention whether migrations, cache clearing, queue restart, plan review, or addon updates are required.

Update Testing Checklist

Back up files and database.
Test login, registration, forms, responses, funnels, surveys, QR redirects, share links, embed codes, lead capture, automations, webhooks, analytics, reports, files, custom domains, billing, marketplace, and admin settings.
Check addon changelogs separately because addons can add migrations, routes, providers, plan fields, or sidebar items.
If something fails after update, clear cache, dump autoload, run migrations, check logs, review package versions, and restore backup if data integrity is at risk.

Buyer Readiness Notes

Before using Changelogs in production, confirm that the application has been installed on the correct licensed domain, cache has been cleared after configuration changes, and all relevant workspace permissions have been tested with realistic user accounts. LeadFlow AI is often used as a customer-facing SaaS product, so a setting that looks internal during setup can affect paid users, published forms, funnel redirects, lead records, invoices, files, domains, or addon visibility.

For agency deployments, prepare a repeatable launch checklist for each workspace. The checklist should include workspace branding, form fields, consent copy, funnel pages, tracking fields, notification recipients, lead assignment rules, reports, file storage, custom domains, support ownership, and team permissions. For SaaS deployments, prepare a platform checklist that covers plans, payment gateways, mail delivery, queue workers, cron, file storage, AI provider settings, marketplace packages, backups, privacy pages, and production debug mode.

When troubleshooting this area, separate configuration problems from data problems. Configuration problems usually involve cache, plan permissions, missing addons, provider credentials, mail settings, queue workers, or route discovery. Data problems usually involve workspace ownership, hidden fields, duplicate slugs, invalid imports, deleted parent records, old embed codes, or team permission rules. Testing with a fresh private browser session and a non-admin account helps confirm the real customer experience.

Operational FAQ

Who should review this page?
Product owners, SaaS admins, agency operators, support staff, and implementation partners should review it before changing related production workflows.

What should be documented internally?
Record any custom domain rules, installed addons, plan limits, payment provider settings, AI provider settings, integration credentials, and client-specific visibility decisions.

What is the safest production habit?
Back up first, change one thing at a time, clear cache when the change affects Laravel configuration or package discovery, then test the exact user or client workflow that depends on the change.