new
App Marketplace
Introducing App Updates with Versioning in the GHL Marketplace
We are introducing App Updates powered by explicit App Versioning in the HighLevel Marketplace.
This release is a foundational platform improvement that enables developers to ship updates safely and allows existing users to upgrade apps without uninstalling and reinstalling. It replaces the legacy Marketplace behavior and establishes a modern, controlled, and transparent update lifecycle.
✅ Important Context: How Updates Worked Before
Previously, the GHL Marketplace did not support in-place app updates. Developers were required to make changes directly on the live app, and while new installations received the latest version, existing installs could not be upgraded. To access updates, users had to uninstall and reinstall the app, which often resulted in:
- Loss of existing configurations
- Disruption to active workflows
- Reluctance to adopt new releases
- Increased operational risk for agencies and sub-accounts
🔮 What’s New
With this release:
- Apps now support in-place updates
- Existing installs can be upgraded safely
- App configuration is preserved during updates
- Users can see what changed before updating
- Developers can release updates without impacting live users
- This brings the Marketplace in line with modern app ecosystems.
✨ Key Capabilities
- Explicit App Versioning
Apps now consist of multiple explicit versions. Each version maintains its own:
- Lifecycle status
- Review record
- Release notes
- Change history
Live versions are never edited directly.
- Version Lifecycle States
Each app version progresses through defined states:
- Draft – Editable working copy
- In Review – Submitted for Marketplace review (public apps)
- Live – Approved and installable
- Deprecated – Scheduled for removal
- Disapproved – Rejected version; editable like Draft
This ensures predictable, auditable releases.
- Version Limits & Safety Rules
To prevent unstable or excessive versions:
- Only one Draft or Disapproved version at a time
- Maximum of 3 total versions per app
- (Live + In Review + Deprecated) ≤ 2
- (Draft + Disapproved + In Review) = 1
These limits protect platform stability and review clarity.
- Creating a New Version
- Developers clone the latest Live version to create a Draft
- All development occurs without impacting production users
- A new Draft cannot be created until the current Draft or Disapproved version is resolved.
- Publishing an Update: Semantic Versioning
Developers must select a version type:
- Major (x.0.0) – Breaking or incompatible changes
- Minor (x.y.0) – Backward-compatible enhancements
- Patch (x.y.z) – Bug fixes only
- Release Notes: Release notes are shown directly to users during the update flow.
User Experience When an Update Is Available
When a new version goes Live:
- Installed apps show an Update button
- Displays version-specific release notes
- Major updates require explicit user confirmation
- Minor and Patch updates follow a standard safe flow
This prevents surprise changes and builds trust.
🧩 Module Update Behavior (Current State)
- Modules are currently associated with the app, not a specific version
- Changes to module functionality may become visible immediately after saving
Guidance
- Use Major versions when introducing new module capabilities
- Use private apps for testing
- Apply changes to live apps only when changes are production-ready
🗑️ Deprecating Old Versions
Live versions can be scheduled for removal with a minimum 3-day notice. On the deprecation date:
- The version is removed
- All installs using that version are automatically uninstalled
- This prevents outdated or unsafe versions from lingering.
🔜 What’s Next
We’re actively working on:
- Version-aware module updates
- Version-aware pricing updates
- Safer release controls and clearer update propagation
This release establishes the foundation for these improvements.
For more details, please check:
https://marketplace.gohighlevel.com/docs/oauth/HowToUpdateYourAPP/index.htmlFor questions or concerns: