Application Versioning and Updates

what changes when a new version is installed.

Versions in Flowlu applications

Each application has versions that define its behavior, permissions, and integration points.

• Private applications (local) always have a single active version.

• Public applications can have multiple versions, but only one version is active at a time.

A new version is required when the application’s functionality, permissions, or manifest configuration changes.

Creating a new version

A new version must be created when you need to change:

• application functionality,

• requested permission scopes,

• integration points,

• webhook configuration,

• backend or frontend behavior that affects users.

Changes limited to texts or visuals do not require a new version (see below).

Version management actions available in the Developer Console include:

• creating a new version,

• editing version details,

• activating or deactivating a version,

• submitting a version for moderation,

• publishing or hiding a version,

• installing a version via link or into the current account.

What requires moderation

For public applications, moderation is required for:

• every new application version,

• changes to functionality,

• changes to requested scopes or permissions.

During moderation, Flowlu reviews:

• declared functionality,

• application operability,

• security considerations,

• whether requested scopes are necessary and justified.

What does NOT require moderation

The following changes do not require moderation and do not require creating a new version:

• application description text,

• support information,

• banners or promotional content,

• logos and visual assets.

These changes can be applied directly to the existing version.

What happens during an update

When a new version is installed:

• the previous and new manifests are compared,

• webhook configuration is updated:

  • webhooks removed from the manifest are unregistered,

  • new webhooks defined in the manifest are registered,

• application settings, user settings, roles, and files are preserved,

• the application stops rendering in integration points removed from the manifest,

• the application starts rendering in new integration points added in the manifest.

No application data is automatically deleted during an update.

Updating installed applications

When an application is already installed in an account:

• administrators receive the updated version according to marketplace rules,

• user access rules and role assignments remain unchanged,

• application configuration remains intact.

Applications do not receive lifecycle event notifications for updates.

Best practices for version updates

Developers are encouraged to:

• increment versions following semantic versioning principles,

• clearly document changes between versions,

• avoid requesting broader scopes than required,

• test updates in a sandbox account before submission.

Careful versioning helps ensure smooth updates and reduces the risk of rejected submissions.