Self-hosted workflows for coding-agent delivery. Orchestrate CodeBuddy, Codex and Claude Code with scripts and human approval gates. Includes Local workflows for coding assistants.
JavaScript agent-orchestrationagentic-workflowai-agentsai-codingclaude-codecode-reviewcodebuddycodexcoding-agentscursordeveloper-toolshuman-on-the-loopllmmcpmulti-agentsdlcself-hostedsopworkflow-automationworkflow-engine
chore(release): prepare v0.3.7 (#202)
cocofhucaa89b75732b
diff --git a/.github/workflows/release.yml b/.github/workflows/release.ymlindex 90798081..65715602 100644--- a/.github/workflows/release.yml+++ b/.github/workflows/release.yml@@ -85,10 +85,41 @@ jobs:username: ${{ github.actor }}password: ${{ secrets.GITHUB_TOKEN }}+ # Personal TCR. TCR_REGISTRY is the host only, for example+ # ccr.ccs.tencentyun.com. The namespace and repository are loopforge/loopforge.+ - name: Check TCR credentials+ id: tcr+ env:+ TCR_REGISTRY: ${{ secrets.TCR_REGISTRY }}+ TCR_USERNAME: ${{ secrets.TCR_USERNAME }}+ TCR_PASSWORD: ${{ secrets.TCR_PASSWORD }}+ run: |+ if [[ -z "${TCR_USERNAME}" || -z "${TCR_PASSWORD}" ]]; then+ echo "TCR_USERNAME and TCR_PASSWORD repository secrets are required" >&2+ exit 1+ fi+ registry="$(printf '%s' "${TCR_REGISTRY}" | tr -d '[:space:]')"+ if [[ ! "${registry}" =~ ^[a-z0-9]([a-z0-9.-]*[a-z0-9])?(:[0-9]+)?$ ]]; then+ echo "TCR_REGISTRY must be the registry host, for example ccr.ccs.tencentyun.com" >&2+ exit 1+ fi+ {+ echo "registry=${registry}"+ echo "image=${registry}/loopforge/loopforge"+ } >> "$GITHUB_OUTPUT"++ - uses: docker/login-action@v4+ with:+ registry: ${{ steps.tcr.outputs.registry }}+ username: ${{ secrets.TCR_USERNAME }}+ password: ${{ secrets.TCR_PASSWORD }}+- uses: docker/metadata-action@v5id: metadatawith:- images: ${{ steps.release.outputs.image }}+ images: |+ ${{ steps.release.outputs.image }}+ ${{ steps.tcr.outputs.image }}flavor: latest=falsetags: |type=semver,pattern={{version}},value=${{ steps.release.outputs.tag }}@@ -124,6 +155,7 @@ jobs:TAG: ${{ steps.release.outputs.tag }}VERSION: ${{ steps.release.outputs.version }}IMAGE: ${{ steps.release.outputs.image }}+ TCR_IMAGE: ${{ steps.tcr.outputs.image }}PRERELEASE: ${{ steps.release.outputs.prerelease }}run: |notes="$(cat <<EOF@@ -135,7 +167,7 @@ jobs:./start.sh\`\`\`- Platform image: \`${IMAGE}:${VERSION}\` (pinned in \`compose.yaml\`). Existing installations: check out \`${TAG}\`, run \`./start.sh\`, and apply the new files under \`migrations/\` listed in [CHANGELOG.md](https://github.com/${GITHUB_REPOSITORY}/blob/${TAG}/CHANGELOG.md).+ Platform image: \`${IMAGE}:${VERSION}\` (pinned in \`compose.yaml\`). Tencent Cloud mirror: \`${TCR_IMAGE}:${VERSION}\`. Existing installations: check out \`${TAG}\`, run \`./start.sh\`, and apply the new files under \`migrations/\` listed in [CHANGELOG.md](https://github.com/${GITHUB_REPOSITORY}/blob/${TAG}/CHANGELOG.md).EOF)"if gh release view "${TAG}" >/dev/null 2>&1; thendiff --git a/CHANGELOG.md b/CHANGELOG.mdindex 757b154f..ee29dbf1 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -1,6 +1,16 @@# Changelog-Platform releases use `vX.Y.Z` tags and publish `ghcr.io/tencent/loopforge`. LoopForge Local packages use `local-vX.Y.Z` tags and are published by manually running the `release-local` workflow.+Platform releases use `vX.Y.Z` tags and publish `ghcr.io/tencent/loopforge`, mirrored to `ccr.ccs.tencentyun.com/loopforge/loopforge`. LoopForge Local packages use `local-vX.Y.Z` tags and are published by manually running the `release-local` workflow.++## 0.3.7 — Tencent Cloud image mirror++- Platform releases also push `ccr.ccs.tencentyun.com/loopforge/loopforge` with the same tags as `ghcr.io/tencent/loopforge`. `compose.yaml` still pins GHCR. Install from Tencent Cloud with `LOOPFORGE_IMAGE=ccr.ccs.tencentyun.com/loopforge/loopforge:0.3.7 ./start.sh`.+- A running SOP node animates its activity on the graph.+- Approving a run reloads the queue from the server, so the waiting card disappears once execution continues.+- LoopForge Local's Classic CodeBuddy hook keeps manual gates when PyYAML is not installed.+- The TKE node-pool tool keeps the SDK error and CAM hint when its fallback query fails.++No migrations are required.## 0.3.6 — a default sandbox on an uninitialized catalogdiff --git a/compose.yaml b/compose.yamlindex 7b01d42d..2aaa339c 100644--- a/compose.yaml+++ b/compose.yaml@@ -21,7 +21,7 @@ services:profiles: [platform]# Published release stack: never builds. Bump the pinned tag (here and in# AGENTFLOW_ISOLATED_IMAGE) with each release; source builds use compose.dev.yaml.- image: ${LOOPFORGE_IMAGE:-ghcr.io/tencent/loopforge:0.3.6}+ image: ${LOOPFORGE_IMAGE:-ghcr.io/tencent/loopforge:0.3.7}ports:- "${LOOPFORGE_BIND:-0.0.0.0}:${AGENTFLOW_HTTP_PORT:-8090}:8080"environment:@@ -40,7 +40,7 @@ services:AGENTFLOW_PLATFORM_MCP_URL: ${AGENTFLOW_PLATFORM_MCP_URL:-http://platform:8080}AGENTFLOW_DOCKER_NETWORK: ${COMPOSE_PROJECT_NAME:-loopforge}_defaultAGENTFLOW_LOCAL_SANDBOX: docker- AGENTFLOW_ISOLATED_IMAGE: ${LOOPFORGE_IMAGE:-ghcr.io/tencent/loopforge:0.3.6}+ AGENTFLOW_ISOLATED_IMAGE: ${LOOPFORGE_IMAGE:-ghcr.io/tencent/loopforge:0.3.7}HOME: ${LOOPFORGE_DATA_DIR:?Run scripts/configure.sh first}/homeAGENTFLOW_RUNNER_BINARY: /app/bin/agentflow-runner-{os}-{arch}AGENTFLOW_GATE_MCP_BINARY: /app/bin/agentflow-gate-mcp-{os}-{arch}diff --git a/docs/deployment.md b/docs/deployment.mdindex ace3f09e..f87edec6 100644--- a/docs/deployment.md+++ b/docs/deployment.md@@ -35,11 +35,11 @@ The installer checks Docker, Compose, Python 3 and curl. It offers to install miRun it as the installation owner, including an ordinary Linux user. If that user cannot access Docker directly, the installer validates sudo and uses `sudo -n docker` consistently for Compose, schema installation and seeds. Before each operation it checks whether sudo credentials expired during a long build, prompting again in a terminal or failing with instructions in unattended mode. It does not require adding the user to the Docker group or logging out. For unattended installations run `sudo -v` first; `LOOPFORGE_YES=1` accepts installation prompts but does not bypass operating-system permissions. Without sudo or Docker access it fails immediately with instructions. Rootless Docker uses its active context's Unix socket; remote Docker contexts need a separately configured deployment because sandbox workspaces are local bind mounts.-`compose.yaml` is the published-image stack and never builds: `./start.sh`, `scripts/install.sh` and a plain `docker compose --profile platform up` all pull the GHCR release pinned there (currently `ghcr.io/tencent/loopforge:0.3.6`). The pin matches the checkout's migrations and seeds, so check out a release tag when you install. Set `LOOPFORGE_IMAGE` (for example to an `@sha256:` digest) only to override it; a value saved in `.env` takes precedence over later pin changes.+`compose.yaml` is the published-image stack and never builds: `./start.sh`, `scripts/install.sh` and a plain `docker compose --profile platform up` all pull the GHCR release pinned there (currently `ghcr.io/tencent/loopforge:0.3.7`). The pin matches the checkout's migrations and seeds, so check out a release tag when you install. Set `LOOPFORGE_IMAGE` (for example to an `@sha256:` digest, or to `ccr.ccs.tencentyun.com/loopforge/loopforge:0.3.7`) only to override it; a value saved in `.env` takes precedence over later pin changes.`./start.sh dev` (or `LOOPFORGE_BUILD_FROM_SOURCE=1 bash scripts/install.sh`) builds this checkout as `loopforge-platform:local` from `compose.dev.yaml`. It saves `COMPOSE_FILE=compose.yaml:compose.dev.yaml` in `.env`, so later runs and plain `docker compose` commands keep using the source build until `./start.sh release`. Source builds reuse npm, Go module and Go compiler caches.-Pushing a `vX.Y.Z` tag on `main` runs the `release` workflow once the `platform` workflow has passed on that commit. The tagged `compose.yaml` must already pin `loopforge:X.Y.Z`. It publishes `ghcr.io/<owner>/loopforge` as `X.Y.Z`, `X.Y`, `latest` and `sha-<commit>`, smoke-tests the pushed digest with `./start.sh`, and creates the GitHub Release. Forks publish under their own owner; set the GHCR package visibility/access for your team before distributing the image. Images are pulled only when missing by default; use an immutable tag/digest, or set `LOOPFORGE_PULL_POLICY=always` when updating a mutable tag. Existing `.env` values take precedence; change the saved image or URL there when updating an installation. Compose waits for the API's health check with a bounded timeout before installing schema extensions and seeds.+Pushing a `vX.Y.Z` tag on `main` runs the `release` workflow once the `platform` workflow has passed on that commit. The tagged `compose.yaml` must already pin `loopforge:X.Y.Z`. It publishes `ghcr.io/<owner>/loopforge` and the same tags on `ccr.ccs.tencentyun.com/loopforge/loopforge` (`X.Y.Z`, `X.Y`, `latest` and `sha-<commit>`), smoke-tests the pushed GHCR digest with `./start.sh`, and creates the GitHub Release. Forks publish under their own owner; set the GHCR package visibility/access for your team before distributing the image. Images are pulled only when missing by default; use an immutable tag/digest, or set `LOOPFORGE_PULL_POLICY=always` when updating a mutable tag. Existing `.env` values take precedence; change the saved image or URL there when updating an installation. Compose waits for the API's health check with a bounded timeout before installing schema extensions and seeds.Open the platform and create the first account in the browser; it receives platform administration. Until that account exists the login page only offers this setup step.