Buyers of source code worry about one thing more than any other: will this product still be maintained after I pay? You answer that with three habits. Use semantic versioning so the version number tells buyers how risky an update is. Keep a changelog that explains every release in plain language. And publish a support policy that says what help is included, for how long, and what is not included.
These habits turn a one-time sale into a relationship, and they are a big part of what makes buyers trust a listing, as described in our guide on how to sell your web app or SaaS source code. This article covers the mechanics: numbering releases, writing changelog entries, packaging updates for customized installs, and setting support limits that protect your time.
How does semantic versioning apply to a web app?
Semantic Versioning uses three numbers, MAJOR.MINOR.PATCH. The specification was written for libraries with a public API, so you need to decide what your "public API" is when you sell a whole application. For a source code product, it is everything a buyer depends on when they install, configure, customize and upgrade:
- Server requirements (language, database and extension versions).
- Environment variables and configuration keys.
- Database schema that buyers may query or extend.
- Extension points: hooks, events, override folders, theme files, documented classes.
- Your REST API, webhooks and import or export formats.
A change that forces buyers to change any of these is a breaking change, even if the app looks the same.
| Change | Version bump | Example |
|---|---|---|
| Bug fix with no change to requirements, config or extension points | PATCH (2.4.1 to 2.4.2) | Fix wrong totals on the monthly report |
| Security fix that is backward compatible | PATCH | Add missing authorization check on export route |
| New feature; existing installs keep working after migrations | MINOR (2.4.2 to 2.5.0) | Add SMS reminders as an optional module |
| New optional setting or environment variable with a safe default | MINOR | Add REPORTS_CACHE_MINUTES, default 10 |
| Raised minimum PHP or database version | MAJOR (2.5.0 to 3.0.0) | Require PHP 8.4 |
| Renamed config key, removed hook, changed API response | MAJOR | Rename MAIL_FROM handling; remove deprecated v1 API |
| Framework major upgrade that changes override paths | MAJOR | Move to a new framework major version with a new folder layout |
Two practical rules help: deprecate before you remove (warn in one MINOR release, remove in the next MAJOR), and keep MAJOR releases rare and well documented. Buyers forgive breaking changes; they do not forgive surprises.
Write a changelog buyers can trust
A changelog is written for people, not generated from commit messages. The widely used Keep a Changelog format groups changes under Added, Changed, Deprecated, Removed, Fixed and Security, with the newest release at the top and a date for each version. Here is an example of what good entries look like:
[3.0.0] — 2026-11-10
Upgrade notes: requires PHP 8.4. Run migrations. The
MAIL_FROMsetting moved to Settings > Email; existing values are migrated automatically. If you overrideresources/views/invoices, compare your copy with the new template.Added — Recurring invoices with automatic reminders. — Japanese translation.
Changed — Invoice PDF layout now supports long item descriptions.
Removed — The v1 REST API, deprecated in 2.6.0. Use v2.
Security — Exported CSV files are now only available to users with the Reports permission.
[2.6.1] — 2026-09-22
Fixed — Calendar showed bookings one hour off after a daylight saving change.
Notice the details: the date, upgrade notes before the list, the exact setting that moved, the folder that may need attention, and why something was removed. "Bug fixes and improvements" tells a buyer nothing and signals that you may not know what changed either.
Publish the changelog in three places: as a file in the download, on your listing, and inside the app's admin area if you have an update notice. A recent dated entry on the listing is one of the strongest signals that the product is alive.
Ship updates buyers can actually apply
Source code buyers customize. If your update process assumes an untouched install, every release becomes a wave of support tickets. Design for customization from the start.
Give customizations a safe place to live
- Override folders for views, translations and themes that your code checks before its own defaults.
- Events and hooks at important points (invoice created, user registered) so buyers can add behavior without editing core classes.
- Configuration and settings for anything a buyer would reasonably want to change.
- A custom service provider or module folder that updates never overwrite.
Document these extension points; our guide to documentation that cuts support tickets shows how to write the customization guide.
Package each release properly
- Full package: the complete code for new installs and for buyers who never customized.
- Upgrade notes: requirements changes, migrations, new settings, changed files buyers may have overridden.
- A list of changed files since the previous release, so buyers who edited core files know what to compare.
- Database migrations that run safely on existing data, and are tested on a copy of a realistic database.
- A recommended upgrade workflow: back up files and database, put the app in maintenance mode, replace files, run migrations, clear caches, test, bring it back up.
For buyers who use Git, suggest keeping your original release on a separate branch and merging each new release into their customized branch. Conflicts then show exactly where their changes meet yours. If your product is built on Laravel, link to the framework's own upgrade guide in your notes whenever a release moves to a new framework major version.
Tell buyers an update exists
On AppTrovo, you publish a new version of your product and buyers can download new versions while their support and update period is active. You can also show an update notice inside your app: the public product API returns the current version, so your admin area can compare it with the installed version and link to the changelog. Check at most once a day, and never block the app if the check fails. The license integration guide includes an example.
Release checklist
- Choose the version number using the table above.
- Write the changelog entry and upgrade notes.
- Run tests, then install the release on a clean server.
- Upgrade a copy of the previous version with realistic data and a few overrides in place.
- Update documentation and screenshots that changed.
- Build the package from a tagged commit, without development files, logs or secrets.
- Deploy the same build to your live demo.
- Upload the new version and update the listing's changelog.
- Watch tickets closely for 48 hours and be ready with a PATCH release.
Write a support policy that sets fair limits
Without a written policy, "support" grows to include custom development, server administration and teaching. A short policy on your listing and in your docs prevents that, and buyers appreciate knowing what to expect. On AppTrovo, each product has an included support period that you configure (6 months by default), and you can let buyers buy longer support at checkout or extend it later.
Here is a template you can adapt:
Support policy
Included: help installing the product on a supported server; answers to questions about features and settings; fixes for bugs in the original code; security updates; guidance on where to make common customizations.
Not included: custom development or new features for a single buyer; fixing problems caused by modifications to the code; server, hosting or email provider setup beyond our documented requirements; third-party plugins or services.
How to get help: open a support ticket from your purchase. Include your product version, server environment (PHP and database version), the exact error message and the steps to reproduce it.
Response target: we aim to reply within two business days, Monday to Friday, in English. Complex issues may take longer to resolve.
Support period: support and updates are included for the period shown on the product page and can be extended from your dashboard.
Set a response target you can actually meet, including during holidays. A reliable two-day reply is better than a promised one-hour reply you miss. If you offer paid customization, mention it separately so buyers know where to go.
Support time is a real cost of every sale. As an illustrative example, if an average buyer opens three tickets that take twenty minutes each, every sale costs you an hour of work during the support period. Estimate that number from your first months of tickets and factor it into your price; our guide on how to price source code shows how. Also make sure the policy does not contradict the marketplace's license terms, which define what buyers may do with the code.
Make tickets efficient
- Ask for version, environment, exact error and steps in the ticket form itself.
- Add a system information page to the admin area that buyers can copy into a ticket.
- Answer with a documentation link plus a short summary, and improve the page if the link did not help.
- Reply to reviews and questions in public when the answer helps future buyers too.
Handle security issues differently
Security fixes deserve their own process, because buyers run your code on their servers with their customers' data.
- Publish a way to report vulnerabilities, such as a dedicated email address in your docs. A
security.txtfile, defined in RFC 9116, is a standard place to put it on your website. - Fix first, then disclose. Release the PATCH, then describe the issue in the Security section of the changelog with enough detail for buyers to judge urgency, but without a step-by-step exploit.
- Fix older supported versions when practical, or clearly tell buyers which version they must move to.
- Tell buyers to update through every channel you have: the listing, the in-app notice and your support replies.
Plan for end of life
No product is maintained forever. Decide in advance how you will end support for an old major version or for the whole product. Announce it in the changelog, give buyers a reasonable notice period, and publish a final release with all known security fixes. On AppTrovo, a product that has issued licenses can be retired rather than deleted: it is unlisted, but every existing license keeps verifying, so buyers' installations are not affected.
Frequently asked questions
What is semantic versioning in simple terms?
It is a numbering scheme, MAJOR.MINOR.PATCH, where each number tells users what kind of change a release contains. PATCH means bug fixes only, MINOR means new features that keep existing setups working, and MAJOR means something changed that may require work from the user when they upgrade.
What should a changelog include?
Each release needs a version number, a date and grouped entries for what was added, changed, deprecated, removed, fixed and secured. For applications that buyers install themselves, add upgrade notes at the top of each release: new requirements, migrations, moved settings and files that customized installs should compare.
How often should I release updates?
Release PATCH fixes as soon as they are ready, especially for security issues. Many sellers bundle features into MINOR releases every one to three months, which gives buyers a predictable rhythm. Regular, dated releases matter more than frequent ones.
Do buyers have to pay for updates?
On AppTrovo, buyers can download new versions while their support and update period is active, and they can extend that period. Once it ends, they keep the version they have and can continue using it under their license.
Should support include help with customizations?
Most sellers include guidance on where to make common changes but exclude writing custom code for individual buyers. Say this clearly in your support policy. If you want to offer customization work, present it as a separate paid service.