Skip to content

LoopForge v0.4.1-rc.1

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Nov 16:08
· 0 commits to main since this release

New installation

git clone --branch v0.4.1-rc.1 https://github.com/Tencent/LoopForge.git
cd LoopForge
./start.sh

Platform image: ghcr.io/tencent/loopforge:0.4.1-rc.1 (pinned in compose.yaml).

Digest: ghcr.io/tencent/loopforge@sha256:b9b098a289f5a83503d1539929b616115cc68d1e07eadacb2036008a186fa419.

Where ghcr.io is slow, set MIRROR to a registry host that replaces it (for example MIRROR=ghcr.nju.edu.cn ./start.sh). This trusts that host: the download is tagged as the pinned name. Check it with docker image inspect --format '{{index .RepoDigests 0}}' ghcr.io/tencent/loopforge:0.4.1-rc.1 and compare the digest after @.

Upgrade from v0.4.0

Use your existing Compose checkout with its original .env and data volumes. Stop any separately deployed workers and keep MySQL running. If you use a LOOPFORGE_IMAGE override, update it to ghcr.io/tencent/loopforge:0.4.1-rc.1 or the digest above.

git fetch origin tag v0.4.1-rc.1 &&
git switch --detach v0.4.1-rc.1 &&
docker compose stop platform &&
docker compose exec -T mysql sh -c 'MYSQL_PWD="$MYSQL_PASSWORD" mysql -u loopforge loopforge' < migrations/036_git_http_credentials.sql &&
./start.sh pull

Restart any separate workers on the new version and verify private repository access with an existing GitHub credential. Run 037_retire_plain_git_token.sql manually after verification and the rollback window. See the credential migration guide and changelog.

What's Changed

New Contributors

Full Changelog: v0.4.0...v0.4.1-rc.1