v1.4.0 Pre-release

v1.4.0 EA (Pre release)

The update content of the Pre-Release version has not been frozen and may be adjusted at any time.

Release Date

2024.07.12 - 2024.07.14

New

• [version-controller] add argument channel
• [version-family-builds-controller] New API

Components Version

• [Public API] v1.3.0 => v1.4.0

v1.3.2

Change

• [Family Database] Remove id field

Upgrade

The database formats from v1.2.0 to v1.3.2 are incompatible and cannot be upgraded automatically. The reason for the incompatibility is that the id field structure in the version_families table has been updated.

v1.3.1

v1.3.1

Change

• [Mars] Mysql dependency update
• [External Download API (Private)] Improved UUID generation mechanism

Components Version

• [Private API] v1.3.0 => v1.3.1

v1.3.0

v1.3.0

New

• [Download API (Private)] All Recycled (after successful call, default: false)
• [Download API (Public/Private)] Support third-party link download
• [Family API (Public)] version-family-controller support
• [Mars] TLS Support (Experimental)
• [ExternalDownload API (Private)] New API -> Private Download API supporting third-party links

Change

• [Download API (Private)] Adjust GC position
• [Download API (Private)] BuildID can no longer be 0

Components Version

• [Private API] v1.1.0 => v1.3.0
• [Public API] v1.2.0 => v1.3.0

Upgrade

The configuration format from v1.2.0 to v1.3.0 is incompatible and cannot be upgraded automatically.

v1.2.0

New

• [Download API (Private)] Active GC (after successful call, default: false)

Fix

• [Download API (Private)] The generated ID cannot be used in some cases
• [Download API (Private)] The pointer offset caused by hash calculation makes the written file empty

Change

• [Build API (Private)] Initial buildID changed from 0 to 1
• [Mars] No longer provide v2, v3 build packages

Upgrade

The database formats from v1.1.0 to v1.2.0 are incompatible and cannot be upgraded automatically. The reason for the incompatibility is that the id field structure in the builds table has been updated.

The configuration format from v1.1.0 to v1.2.0 is incompatible and cannot be upgraded automatically.

Tips

fasthttp will cause the file to remain in memory after being read, but will not continue to be expanded. It is used as a buffer, so bodySize needs to be set in advance. Or enable active GC.

v1.1.0

New

• [Download API (Private)] There can now be multiple files in a Downloads structure
• [Download API (Public)] The corresponding document can be downloaded by specifying the ID
• [Server] Support setting the maximum size of files that can be uploaded simultaneously (default: 120(MB))

Change

• [Download API (Private)] Deprecated filename parameter

Upgrade

The database formats from v1.0.0 to v1.1.0 are incompatible and cannot be upgraded automatically. The reason for the incompatibility is that the downloads field structure in the builds table has been updated.

The configuration format from v1.0.0 to v1.1.0 is incompatible and cannot be upgraded automatically.

v1.0.0