v1.4.2

v1.4.2

The new Golang compiler breaks my cross-compilation toolchain, that's why no arm64 builds on linux are provided.

New

• {build} in version-build-controller and download-controller can be latest

Change

• Golang compiler upgrade: v1.22.5 => v1.23.0
• Dependency Updates

v1.4.1

v1.4.1

Because of this problem, I have troubled it for nearly six hours. I have no more energy. The file scan will not upload for the time being

Fix

• [External Download API (Private)] Due to the failure of the File field, the reading fails
• [External Download API (Private)] When checking the Filename (name) and SHA256, I still trigger the sniff
• [External Download API (Private)] Unexpected data in the sniffing mode causes a lot of garbage

v1.4.0

v1.4.0

I re-set up the toolchain and automation so I can now provide builds for amdv1-v4 again, and additionally provide arm64 builds.

Starting from v1.4.0, some components start to use SIMD acceleration, using processors that support avx512, and the amdv3/amdv4 build package can achieve better performance. At the same time, json processing also supports SIMD acceleration.

New

• [version-controller] add argument channel
• [version-family-builds-controller] New API
• [External Download API (Private)] Actively sniff filenames/file hashes (default: false)
• [External Download API (Private)] Selectable file name (only available if active sniffing is not enabled or if no file name was detected)
• [Download API (Public)] Downloadable using file name
• [Mars] Sha256 processing now supports SIMD acceleration
• [Mars] Optional json runtime
• [Mars] (json runtime) sonic optional JITPreTouch

Change

• [External Download API (Private)] active_gc is now also available
• [All Download API (Private)] active_gc is now enabled by default
• [Mars Network] Optimize proxy reading mechanism. When using proxy tools on Windows platform, it is no longer necessary to set http_proxy parameters.

Fix

• [External Download API (Private)] a possible memory leak in v1.4.0-Preview

Components Version

• [Private API] v1.3.1 => v1.4.0
• [Public API] v1.3.0 => v1.4.0
• [Configure] v1.3.0 => v1.4.0

Upgrade

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

v1.3.2

Change

• [Family Database] Remove id field

Components Version

• [Database] v1.2.0 => v1.3.2

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