Skip to content

feat: add X-LaunchDarkly-Instance-Id header to server SDK (SDK-2353) #1907

feat: add X-LaunchDarkly-Instance-Id header to server SDK (SDK-2353)

feat: add X-LaunchDarkly-Instance-Id header to server SDK (SDK-2353) #1907

Re-run triggered May 28, 2026 19:55
Status Success
Total duration 19m 32s
Artifacts

server.yml

on: pull_request
contract-tests
4m 47s
contract-tests
contract-tests-curl
4m 4s
contract-tests-curl
build-test-server
8m 52s
build-test-server
build-test-server-curl
8m 25s
build-test-server-curl
build-test-server-mac
6m 18s
build-test-server-mac
build-test-server-mac-curl
5m 26s
build-test-server-mac-curl
build-test-server-windows
19m 44s
build-test-server-windows
build-test-server-windows-curl
19m 25s
build-test-server-windows-curl
Fit to window
Zoom out
Zoom in

Annotations

1 warning
build-test-server-windows-curl
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@08eba0b27e820071cde6df949e0beb9ba4906955, ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/