Apply for release

Submit your mini program version for release to the selected target app and environment. Releases to the production and sometimes the sandbox (if available) environments require approval from the super app.

Before you begin

Ensure you meet the following prerequisites:

  • Access: You must be either:
    • Workspace admin for the workspace where the mini program was created.
    • Admin for the mini program you want to release.
  • Release status: The release status must be New Version Created. To achieve this status, you must have already completed Select target and edit configuration.
  • Version details: All details (including information, configuration, and features) for this mini program version are complete and up-to-date. You also have a final opportunity to review and update some key details in the release request form. Changes made after the application can only be applied to the current version by withdrawing and reapplying, or to future versions. For more information, see:

Procedure

To apply for release, follow these steps:

Step 1: Navigate to the mini program version list

  1. Log in to Mini Program Platform and navigate to the target workspace.
  2. In the left navigation panel, click Mini Programs.
  3. On the page that appears, find the target mini program in the list. You can use the search field to locate it quickly.
  4. Click the name of the mini program to open its details page.
  5. Click the Versions tab. You will see a list of all the created versions.

Step 2: Submit a release request

  1. In the version list, locate the target mini program version.
  2. Click plus (1).png (the plus sign) beside the version number to see the existing releases.
  3. Locate the specific release by reviewing the Target App and Environment columns.
  4. Click Release.
  5. On the release progress page that appears, click Apply to Release.

Tips: If this is the first time the page is being accessed in your workspace, the button might take a few seconds to appear after the system completes building the mini program package.

  1. Review the following key information and update as needed:
    • Basic Information:
      • For Production releases, to help the super app review your update, it is recommended to add Release Notes.
      • To update details other than Release Notes, click Modify, make changes in the new tab, and return to the current page to proceed.
    • Authorized Server Domains, Authorized WAP URLs, and Environment Variables (if applicable): Ensure the displayed settings match your intended release-specific configuration. If changes are needed, update the configuration as described in Select target and edit configuration, and then refresh the current page to proceed.
  1. Click Apply.

If your selected environment requires review, your request will be sent to the super app. See the following table to learn whether a review is required for a specific environment:

Environment

Review required

Development

No

Test

No

Sandbox

Sometimes (varies by target app)

Production

Yes

If a review is required, the release status updates to Under Review. Then, proceed to Step 3 to track your request.

(Optional) Step 3: Track your release request and get approval

If your request is under review, wait for the super app's approval. You can track your request progress in any of the following places:

  • In Mini Program Platform:
    • On the release progress page: The status indicator and release log update once the super app completes processing your request. To see the request details, you can click View Details next to the request submission log.
    • On the Approvals > My Requests page: This page lists all requests from your account, along with their statuses. Find and click the target release request to view its details.
  • Via the inbox of your account email: You will receive an email confirmation once the super app completes processing your request.

If your request is rejected, review the rejection reason, address the stated issues, and reapply. Based on the specific issues, you need to do either of the following:

  • If the issues only relate to the mini program details that are provided within the platform, update these details and reapply to release the current version.
  • If any code issue exists for a DSL mini program, update your code in the IDE, upload it to the platform to create a new version, and then apply to release this new version. For code upload instructions, see Upload code for DSL mini programs.

Tip:

  • If you need to update your mini program details during review and apply the changes to the current version, you can withdraw your release request and reapply.
  • During manual review, the super app will check your mini program for compliance with guidelines and security requirements. When the check completes, you can view the reports from the release log.

What happens next

The next steps depend on the environment and the target app's specific workflow. See the following table for details:

Environment

What happens next

Development

The version is released automatically. The process is complete, and no further action is needed.

Test

Sandbox

Varies as some target apps might support pilot testing as an additional step in the release process.

  • If pilot testing is supported (the release status updates to Pilot Testing), follow the instructions in Conduct pilot testing to proceed.
  • If pilot testing is not supported (the release status updates to Full Release), the version is released automatically. The process is complete, and no further action is needed.

Production

Varies as some target apps might support pilot testing as an additional step in the release process.

  • If pilot testing is supported (the release status updates to Pilot Testing), follow the instructions in Conduct pilot testing to proceed.
  • If pilot testing is not supported (the release status updates to Release Preparation), follow the instructions in Go live to proceed.