From 66b3bf25a0fe2a28d89742d4fbb4bcb529ba6e2e Mon Sep 17 00:00:00 2001 From: jsonbailey Date: Fri, 14 Aug 2026 17:09:02 -0500 Subject: [PATCH] chore: Track the latest v3 contract test release instead of a pinned alpha The FDv2 contract test job pinned sdk-test-harness to v3.0.0-alpha.6, which means every harness release needs a manual bump here. In practice the pin went stale and the job skipped all v3.1.x and v3.2.x tests. The harness downloader resolves a partial version against the Releases API and includes prereleases, so "v3" selects the newest v3 release. The FDv1 job in this repo already floats the same way on the action default of "v2". --- .github/workflows/common_ci.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/common_ci.yml b/.github/workflows/common_ci.yml index c68d6850..c39f75f7 100644 --- a/.github/workflows/common_ci.yml +++ b/.github/workflows/common_ci.yml @@ -66,7 +66,7 @@ jobs: enable_persistence_tests: 'true' test_service_port: ${{ env.TEST_SERVICE_PORT }} token: ${{ secrets.GITHUB_TOKEN }} - version: v3.0.0-alpha.6 + version: v3 - name: Upload test service logs uses: actions/upload-artifact@v4