> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: About App Versioning

## Article: About App Versioning

## Article Link: https://dev.wix.com/docs/build-apps/manage-your-app/versioning/about-app-versioning.md

## Article Content:

# About App Versioning
During your app's life cycle, from bug fixes to new features to promotions, there are different reasons you may need to release a new version of your app. Wix categorizes releases as major or minor and handles versioning accordingly. 

Versioning your app follows the same process the same whether your app is private, unlisted or listed in the App Market.

## Version release types

There are 2 types of app version releases:

- Major version release
- Minor version release

### Major version release

Major updates are not pushed automatically and require user action. Users receive notifications about available version releases in the **Manage Apps** page and must click the **Update** button to accept the new version release.

You can also include a call to action within your app to prompt them to update to the latest version, redirecting them to `https://wix.com/app-installer?appId={appId}`.

If you’re using [custom authentication (legacy)](https://dev.wix.com/docs/build-apps/develop-your-app/access/authentication/custom-authentication-legacy.md), you also need to take the site owner through the OAuth flow. You will receive an authorization code with which you must request a new refresh token. Store the refresh token in your database for later use together with the site owner's instance ID.

Major version numbering: 2.10.0. In this example, '2' denotes the major version.

You can always decide that a change to your app should be considered a major version and require user action for installation, but this isn't recommended, as users won't always update.

### Minor version release
Most version releases are considered minor. Wix users that have installed the latest major version, automatically receive minor releases on top of that version. If they are not on the latest major version, they will be offered to update with the Update button on the Manage Apps page. This will provide the release via the major version release flow, including any new minor releases.

Minor version numbering: **2.10.0.** In this example, **'10'** denotes the minor version.

## App changes and corresponding version types

Below is a list of changes you might implement in your app, along with the corresponding version types they require:

|Minor version |Major version (use sparingly) |
|---|---|
| - Changes to translations <br> - Changes to app company info <br> - Adding, changing or removing [extensions](https://dev.wix.com/docs/build-apps/develop-your-app/extensions/about-extensions.md) <br> - Adding, changing, or removing [webhooks](https://dev.wix.com/docs/build-apps/develop-your-app/api-integrations/events-and-webhooks/about-webhooks.md) or CLI [event extensions](https://dev.wix.com/docs/wix-cli/guides/extensions/backend-extensions/events/add-event-extensions.md) <br> - Changes to pre-installed automations <br> - Removing [permissions](https://dev.wix.com/docs/build-apps/develop-your-app/access/authorization/about-permissions.md) | - Adding [permissions](https://dev.wix.com/docs/build-apps/develop-your-app/access/authorization/about-permissions.md) <br> - Adding an [Embedded Script extension](https://dev.wix.com/docs/build-apps/develop-your-app/extensions/site-extensions/embedded-scripts/about-embedded-scripts.md) <br> - Changes to [Dynamic Parameters of an Embedded Script](https://dev.wix.com/docs/build-apps/develop-your-app/extensions/site-extensions/embedded-scripts/about-embedded-scripts.md#dynamic-parameters)|

You can always choose to release a major version even if the changes to your app can be considered a minor version - however this generally isn't recommended, as it requires users to actively update your app, and they don't always do so.

### App changes that don't trigger a new version

The following changes are pushed to users immediately and don't require a version release:

- Changes to OAuth endpoints (if using custom authentication (legacy))
- Adding or removing app team members 
- Changes to app contact info
- Changes to market listing details

The following changes require submission to the Wix App Market for review, but don't require a version release:

- Changes to pricing

### How to know if your change requires a version release

If you've made a change to a self-hosted app that requires a version release, you'll see that you have a version that isn't updated in the **Distribute** page. 

If you've made a change to a Blocks app, you'll see that the **Release** button is enabled in the Blocks Editor.

<!-- 
If you've made changes to an app in the Wix CLI, run [`wix app release`](https://dev.wix.com/docs/wix-cli/legacy/wix-cli-for-apps/app-development/command-reference.md#release).
-->

## See also
- [About app distribution](https://dev.wix.com/docs/build-apps/launch-your-app/app-distribution/about-app-distribution.md)
- [Release a new app version](https://dev.wix.com/docs/build-apps/manage-your-app/versioning/release-a-new-app-version.md)