Docs / Release Checklist

Release Checklist

This page is the final release gate for Vendventory v1.0.0. Use it before generating the buyer archive, handing the app to a client, or submitting the build to CodeCanyon review.

Release rule: do not package a build until install flow, mail delivery, permissions, inventory modules, notifications, branding, and documentation have all been reviewed together.

1) Detailed Release Pages

Clean Install Smoke

Use the step-by-step blank-database checklist for essential-only and demo-content installs.

Open Checklist

Buyer ZIP Audit

Review what the marketplace archive must include, what it must exclude, and how to keep it shared-hosting friendly.

Open Checklist

Manual QA Checklist

Run the final browser and workflow checks after the automated suite is already green.

Open Checklist

2) Release Gates

Product and branding

Confirm logos, product name, favicon, footer text, and documentation titles match the shipped brand.
Verify the README, changelog, release checklist, and doc version badge all show the same release number.
Check that no template promo widgets, third-party marketing links, or stale placeholder text remain in the live UI.
Verify installer copy, default settings, and docs describe the actual shipping behavior.

Code and runtime

Run php artisan test on the exact workspace that will be packaged.
Install frontend dependencies in the packaging workspace and run npm run build before creating the buyer archive.
Rebuild caches, route metadata, and compiled assets only from the exact workspace being archived or deployed.
Confirm queue, mail, and session defaults are suitable for shared hosting and documented clearly.
Verify notifications, password reset, OTP, and admin approval flows on the same build that will be packaged.

3) Critical Surfaces

Pages and modules to inspect before sign-off

Installer, dashboard, settings, roles and permissions, users and profile, and notification dropdown.
Categories, units, suppliers, products, purchases, stock outs, and stock adjustments.
Reports, exports, copilot, SMTP setup, and documentation navigation.

4) Buyer Package Sign-Off

Marketplace handoff

Archive only the files needed for installation, operation, and documentation.
Exclude local environment files, logs, generated caches, and personal workspace clutter.
Make sure the install guide, changelog, support instructions, and version label all match the archive.

5) Final Sign-Off

The build is submission-ready when the installer works from a blank database, the buyer ZIP is clean, automated tests pass, manual QA covers the critical workflows, and the documentation leads the reviewer through the same reality the app ships with.