Skip to content

chore: Update sdk_metadata features#482

Draft
devin-ai-integration[bot] wants to merge 2 commits intov11from
devin/1773423182-update-sdk-metadata-features
Draft

chore: Update sdk_metadata features#482
devin-ai-integration[bot] wants to merge 2 commits intov11from
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 swift-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 ("all other client-side SDKs" → iOS column) and verified against the repository's CHANGELOG.

17 features included (alphabetical): allFlags, appMetadata, autoEnvAttrs, bigSegments, contexts, eventCompression, experimentation, flagChanges, hooks, inlineContextCustomEvents, multiEnv, offlineMode, pluginSupport, privateAttrs, relayProxyProxy, track, variationDetail.

Updates since last revision

Corrected two version numbers and added one new feature, all verified against CHANGELOG.md:

  • appMetadata: 8.06.2.0 — confirmed via CHANGELOG entry "Introduced ApplicationInfo, for configuration of application metadata" under ## [6.2.0]
  • multiEnv: 5.3.15.0 — confirmed via CHANGELOG entry "Support for multiple LaunchDarkly projects or environments" under ## [5.0.1] (which includes the 5.0.0 release notes). Note: multiEnv was also present in the Obj-C era at 2.14.0, but 5.0 was chosen as the Swift SDK rewrite version per reviewer guidance.
  • eventCompression: added at 9.9.0 — confirmed via CHANGELOG entry "Add option to enable compression of event payloads" under ## [9.9.0]

Human review checklist

  • Verify appMetadata: "6.2.0" — changed from the docs table value of 8.0. The CHANGELOG clearly shows ApplicationInfo was introduced in 6.2.0. The 7.0.0 entry later added "Objective C bindings for ApplicationInfo", which may explain why the docs table listed 8.0. Confirm 6.2.0 is correct.
  • Verify multiEnv: "5.0" — changed from 5.3.1. The CHANGELOG shows multi-environment support was added in 5.0.0/5.0.1 (and earlier in 2.14.0 for Obj-C). Confirm 5.0 is the preferred version.
  • Verify eventCompression: "9.9.0" — new feature added. Confirm eventCompression is the correct canonical feature key.
  • Spot-check other introduction versions against CHANGELOG (e.g., hooks: "9.7.2", inlineContextCustomEvents: "9.13", pluginSupport: "9.14")
  • bigSegments: "1.0" represents the docs value "All" (i.e., supported since first stable release). The repo has beta tags back to 0.1.0-beta, but 1.0 was used as the first stable version — confirm this is acceptable
  • pluginSupport: "9.14" is mapped from the "Observability plugin" row in the docs table — verify this is the correct feature key for this SDK
  • Confirm no supported features are missing — the docs table shows empty cells for bootstrapping, migrations, fileDataSource, testDataSource, secureMode, storingData, webProxy, omitAnonContexts, and otel

Describe alternatives you've considered

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

Additional context

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

Co-Authored-By: Aaron Zeisler <azeisler@launchdarkly.com>
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.

0 participants