Skip to content

ci: Run v3 (FDv2) contract tests for server-node via gh-actions#1359

Merged
keelerm84 merged 2 commits intomainfrom
mk/sdk-2328/server-node-v3-contract-tests
May 6, 2026
Merged

ci: Run v3 (FDv2) contract tests for server-node via gh-actions#1359
keelerm84 merged 2 commits intomainfrom
mk/sdk-2328/server-node-v3-contract-tests

Conversation

@keelerm84
Copy link
Copy Markdown
Member

@keelerm84 keelerm84 commented May 6, 2026

Summary

  • Replace the manual feat/fdv2 branch clone in .github/workflows/server-node.yml with a second invocation of launchdarkly/gh-actions/actions/contract-tests pinned to version: v3.0.0-alpha.6, mirroring the python-server-sdk pattern.
  • Order the runs v2-then-v3 and set stop_service: 'false' on the v2 run so the test service stays alive for the v3 run.
  • Drop the redundant -stop-service-at-end from extra_params -- the action injects it via stop_service.
  • Update packages/sdk/server-node/contract-tests/README.md to describe the suppression files in terms of v2/v3 instead of the now-removed feat/fdv2 branch.

Note

Medium Risk
CI behavior changes by switching from a manual harness checkout/build to the contract-tests GitHub Action and adding a second (v3) run; failures or action/version mismatches could break the server-node pipeline.

Overview
Updates the server-node CI contract test workflow to run both v2 and v3 (FDv2) harness suites using the launchdarkly/gh-actions/actions/contract-tests action, removing the previous manual clone/build of the sdk-test-harness feat/fdv2 branch.

The v2 run is configured to keep the test service alive (stop_service: 'false') so a second invocation can execute the v3 alpha harness (version: v3.0.0-alpha.6) with its own suppression list. Documentation in contract-tests/README.md is updated to describe suppression files in terms of v2 vs v3 rather than the removed branch-based flow.

Reviewed by Cursor Bugbot for commit f2d2a6c. Bugbot is set up for automated code reviews on this repo. Configure here.

Replace the manual feat/fdv2 branch clone with a second invocation of
launchdarkly/gh-actions/actions/contract-tests pinned to v3.0.0-alpha.6,
mirroring the python-server-sdk pattern. The v2 run now sets
stop_service: 'false' so the test service stays alive for the v3 run.
@keelerm84 keelerm84 marked this pull request as ready for review May 6, 2026 19:23
@keelerm84 keelerm84 requested a review from a team as a code owner May 6, 2026 19:23
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 6, 2026

@launchdarkly/js-sdk-common size report
This is the brotli compressed size of the ESM build.
Compressed size: 26281 bytes
Compressed size limit: 29000
Uncompressed size: 128971 bytes

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 6, 2026

@launchdarkly/browser size report
This is the brotli compressed size of the ESM build.
Compressed size: 179543 bytes
Compressed size limit: 200000
Uncompressed size: 830815 bytes

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 6, 2026

@launchdarkly/js-client-sdk size report
This is the brotli compressed size of the ESM build.
Compressed size: 31867 bytes
Compressed size limit: 34000
Uncompressed size: 113634 bytes

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 6, 2026

@launchdarkly/js-client-sdk-common size report
This is the brotli compressed size of the ESM build.
Compressed size: 38473 bytes
Compressed size limit: 39000
Uncompressed size: 211104 bytes

The previous pin (v1.0.2) did not recognize the stop_service input and
unconditionally appended -stop-service-at-end, killing the test service
between the v2 and v3 runs.
@keelerm84 keelerm84 merged commit f5dff69 into main May 6, 2026
42 checks passed
@keelerm84 keelerm84 deleted the mk/sdk-2328/server-node-v3-contract-tests branch May 6, 2026 20:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants