Skip to content

chore: Add tag-prefix for react-client-sdk release collection#378

Open
aaron-zeisler wants to merge 1 commit intomainfrom
aaronz/SDK-2015/release-collection-issues
Open

chore: Add tag-prefix for react-client-sdk release collection#378
aaron-zeisler wants to merge 1 commit intomainfrom
aaronz/SDK-2015/release-collection-issues

Conversation

@aaron-zeisler
Copy link

@aaron-zeisler aaron-zeisler commented Mar 11, 2026

The react-client-sdk repo uses prefixed release tags (e.g. launchdarkly-react-client-sdk-v3.4.0) but the metadata didn't specify a tag-prefix, so sdk-meta couldn't collect releases after 3.3.2.

Here's the related pull request in the sdk-meta repository: launchdarkly/sdk-meta#366

Requirements

  • I have added test coverage for new or changed functionality
  • I have followed the repository's pull request submission guidelines
  • I have validated my changes against all supported platform versions

Related issues

Provide links to any issues in this repository or elsewhere relating to this pull request.

Describe the solution you've provided

Provide a clear and concise description of what you expect to happen.

Describe alternatives you've considered

Provide a clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context about the pull request here.


Note

Low Risk
Low risk metadata-only change that affects release discovery/collection for react-client-sdk but not runtime SDK behavior.

Overview
Updates .sdk_metadata.json to include a releases.tag-prefix for react-client-sdk (e.g. launchdarkly-react-client-sdk-), enabling release collection tooling to match the repo’s prefixed tag naming scheme.

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

The react-client-sdk repo uses prefixed release tags
(e.g. launchdarkly-react-client-sdk-v3.4.0) but the metadata
didn't specify a tag-prefix, so sdk-meta couldn't collect
releases after 3.3.2.
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