chore: Track the latest v3 contract test release instead of a pinned alpha - #433
Open
jsonbailey wants to merge 1 commit into
Open
chore: Track the latest v3 contract test release instead of a pinned alpha#433jsonbailey wants to merge 1 commit into
jsonbailey wants to merge 1 commit into
Conversation
…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".
jsonbailey
force-pushed
the
jb/sdk-2922/float-v3-contract-tests
branch
from
August 14, 2026 22:10
7126469 to
66b3bf2
Compare
jsonbailey
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Change the FDv2 contract test job from
version: v3.0.0-alpha.6toversion: v3.Why
The pin means every
sdk-test-harnessrelease needs a manual bump in this repo. It went stale:v3.0.0-alpha.6shipped 2026-04-29, so this job has been skipping every v3.1.x and v3.2.x test since.The harness downloader already handles this.
downloader/run.shresolves a partial version by querying the Releases API, filteringtag_nameon the prefix, and taking the newest match. That endpoint includes prereleases, so partials land on alphas:VERSIONv2v2.39.0v3v3.2.0-alpha.7This is not new ground. The FDv1 job in this repo already floats on the action default of
version: v2and has never pinned a patch.js-corefloatsv3forserver-node,browser,vue, andnode-clienttoday, through the samelaunchdarkly/gh-actions/actions/contract-tests@contract-tests-v1action and the same downloader path.Notes
The
branchinput is deliberately left alone.origin/v2:downloader/run.shandorigin/v3:downloader/run.share the same blob (df4fe4b), so settingbranch: v3would change nothing.This jumps from an April harness build to current, so CI on this PR is the real verification. If new test cases fail, the follow-up is a
--skip-fromsuppression file rather than restoring the pin.SDK-2922
Note
Overview
Updates the Run SDK contract test v3 step in
common_ci.ymlsoversionisv3instead of the pinnedv3.0.0-alpha.6.That aligns the FDv2 job with how v2 contract tests already float on a major version prefix and lets the harness downloader pick the newest matching release (including prereleases), avoiding manual bumps after each
sdk-test-harnessrelease.Reviewed by Cursor Bugbot for commit 66b3bf2. Bugbot is set up for automated code reviews on this repo. Configure here.