Skip to content

chore: Update sdk_metadata features#379

Merged
aaron-zeisler merged 4 commits intomainfrom
devin/1773423182-update-sdk-metadata-features
Mar 17, 2026
Merged

chore: Update sdk_metadata features#379
aaron-zeisler merged 4 commits intomainfrom
devin/1773423182-update-sdk-metadata-features

Conversation

@devin-ai-integration
Copy link
Contributor

@devin-ai-integration devin-ai-integration bot commented Mar 13, 2026

Requirements

  • I have added test coverage for new or changed functionality — N/A, metadata-only change
  • I have followed the repository's pull request submission guidelines
  • I have validated my changes against all supported platform versions — N/A, metadata-only change

Related issues

Part of a cross-repo effort to populate the features field in .sdk_metadata.json for all LaunchDarkly SDKs.

Describe the solution you've provided

Adds a features map to the react-client-sdk entry in .sdk_metadata.json, documenting which SDK features are supported and the version each was introduced. Feature keys use the canonical camelCase names from sdk-meta/products/feature_info.json, and introduction versions are sourced from the SDK features documentation table (JavaScript-based client-side SDKs → React Web column) and verified against the repository's CHANGELOG.

15 features included (alphabetical): allFlags, appMetadata, bigSegments, bootstrapping, contexts, experimentation, flagChanges, hooks, perContextSummaryEvents, pluginSupport, privateAttrs, relayProxyProxy, secureMode, track, variationDetail.

Updates since last revision

Added two new features, verified against CHANGELOG.md:

  • hooks: introduced in 3.7 — confirmed via CHANGELOG entry "Add hook and plugin support" under ## [3.7.0]. Note: this is the LaunchDarkly evaluation hooks feature, distinct from the React hooks (useState/useEffect) added in 2.11.0.
  • perContextSummaryEvents: introduced in 3.8 — confirmed via CHANGELOG entry "Add support for per-context summary events" under ## [3.8.0].

Updated four feature versions per reviewer guidance that version 2.9 was the first actual react-client-sdk release (prior versions were part of js-client-sdk):

  • bigSegments: 1.02.9
  • experimentation: 1.02.9
  • track: 1.02.9
  • relayProxyProxy: 2.20.22.9 — the 2.20.2 entry was a relay proxy bug fix, not the feature's introduction; relay proxy support was available from the first react-client-sdk release.

Human review checklist

  • Verify the 2.9 convention — seven features are listed at 2.9 (allFlags, bigSegments, experimentation, flagChanges, privateAttrs, relayProxyProxy, track). These represent features available from the first actual react-client-sdk release. Confirm this is the correct set and that none should have a different version.
  • Verify pluginSupport: "3.7" — mapped from the "Observability plugin" row in the docs table. Introduced in the same release as hooks. Confirm this mapping is correct.
  • Spot-check non-2.9 introduction versions against the repo's CHANGELOG or release history (e.g., bootstrapping: "2.9.5", secureMode: "2.18", appMetadata: "2.26", contexts: "3.0", variationDetail: "2.21").
  • Confirm no supported features are missing — the docs table shows empty cells for migrations, offlineMode, autoEnvAttrs, fileDataSource, testDataSource, webProxy, and others. Verify these are truly unsupported by this SDK.

Describe alternatives you've considered

N/A — follows the established pattern from other SDKs (e.g., js-core, go-server-sdk).

Additional context


Note

Low Risk
Metadata-only change adding feature/version annotations for the React Web SDK; no runtime code or behavior is modified. Risk is limited to downstream tooling that consumes .sdk_metadata.json potentially relying on these values.

Overview
Adds a new features map under react-client-sdk in .sdk_metadata.json that enumerates supported SDK capabilities (e.g., contexts, hooks, secureMode) and records the version each was introduced.

No runtime code changes; this updates repository metadata used for documentation/tooling.

Written by Cursor Bugbot for commit 9c83a02. This will update automatically on new commits. Configure here.

Co-Authored-By: Aaron Zeisler <azeisler@launchdarkly.com>
@devin-ai-integration
Copy link
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

devin-ai-integration bot and others added 2 commits March 13, 2026 21:53
…rimentation versions

Co-Authored-By: Aaron Zeisler <azeisler@launchdarkly.com>
Co-Authored-By: Aaron Zeisler <azeisler@launchdarkly.com>
@aaron-zeisler
Copy link
Contributor

Devin: For relayProxyProxy, let's set the version to 2.9 for when that feature was introduced. I believe a bug related to relay proxy was fixed in 2.20.2, not the feature's introduction.

Co-Authored-By: Aaron Zeisler <azeisler@launchdarkly.com>
@devin-ai-integration
Copy link
Contributor Author

Done — updated relayProxyProxy from 2.20.22.9. The 2.20.2 entry was a bug fix, not the feature introduction; relay proxy support was available from the first react-client-sdk release.

@aaron-zeisler aaron-zeisler marked this pull request as ready for review March 16, 2026 19:28
@aaron-zeisler aaron-zeisler requested a review from a team as a code owner March 16, 2026 19:28
@aaron-zeisler aaron-zeisler merged commit 58f1f41 into main Mar 17, 2026
4 checks passed
@aaron-zeisler aaron-zeisler deleted the devin/1773423182-update-sdk-metadata-features branch March 17, 2026 15:32
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