Skip to content

deps: update dependency flagsmith/sdk-spec to v0.7.0 - #310

Closed
renovate[bot] wants to merge 2 commits into
mainfrom
renovate/sdk-spec
Closed

renovate[bot] wants to merge 2 commits into
mainfrom
renovate/sdk-spec

Conversation

@renovate

@renovate renovate Bot commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
Flagsmith/sdk-spec minor v0.3.0 → v0.7.0
Flagsmith/sdk-spec workflow minor v0.3.0 → v0.7.0

Release Notes

Flagsmith/sdk-spec

v0.7.0

Compare Source

What's Changed
New Contributors

Full Changelog: Flagsmith/sdk-spec@v0.6.0...v0.7.0

v0.6.0

Compare Source

What's Changed
New Contributors

Full Changelog: Flagsmith/sdk-spec@v0.5.1...v0.6.0

v0.5.1

Compare Source

What's Changed
  • ci: Run the JS client and iOS against main in the compatibility matrix by @​khvn26 in #​12
  • feat: Optionally treat steps an SDK does not implement as expected failures by @​khvn26 in #​11
  • feat: Add a testChange SDK step by @​khvn26 in #​14

Full Changelog: Flagsmith/sdk-spec@v0.5.0...v0.5.1

v0.5.0

Compare Source

What's Changed

Full Changelog: Flagsmith/sdk-spec@v0.4.0...v0.5.0

v0.4.0

Compare Source

What's Changed
New Contributors

Full Changelog: Flagsmith/sdk-spec@v0.3.0...v0.4.0


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from a team as a code owner October 21, 2026 16:36
@renovate
renovate Bot requested review from emyller and removed request for a team October 21, 2026 16:36
@renovate renovate Bot added the sdk-spec Bumps of the Flagsmith SDK behavioural spec label Oct 21, 2026
@khvn26 khvn26 added the openhands For the OpenHands agent to pick up label Oct 21, 2026
@khvn26 khvn26 changed the title deps: update dependency flagsmith/sdk-spec to v0.5.0 deps: update dependency flagsmith/sdk-spec to v0.5.1 Oct 21, 2026
@renovate renovate Bot changed the title deps: update dependency flagsmith/sdk-spec to v0.5.1 deps: update dependency flagsmith/sdk-spec to v0.6.0 Oct 29, 2026
@renovate
renovate Bot force-pushed the renovate/sdk-spec branch from 68ed083 to 2320251 Compare October 29, 2026 10:31
@coderabbitai

coderabbitai Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 7e27441d-7383-4e81-8e61-bf481df0e9da

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

No actionable comments were generated in the recent review.

Recent review info
Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: b13235af-d2ad-480d-93b8-c49d1179d9db
Commits

Reviewing files that changed from the base of the PR and between c9f5df1 and 6a108ea.

Files selected for processing: 2
  • .github/workflows/sdk-spec.yml
  • sdk-spec/steps.mts

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Walkthrough

The SDK specification steps now include client setup with events enabled, experiment flag retrieval, event tracking, and exposure tracking. The SDK specification workflow now uses the reusable workflow and specification reference at v0.6.0.

Priority: Normal

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: Minimal · previous review 6a108

The new specification steps use events-enabled clients, and the runner accommodates buffered event delivery. No actionable merge-blocking risk remains; merge after normal checks pass.

- [ ] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@flagsmithsmith

Copy link
Copy Markdown
Contributor

Spec v0.6.0 adds three @events features: getExperimentFlag, trackEvent and trackExposureEvent. It also adds a Create the SDK client with events enabled step. CI was red only because sdk-spec/steps.mts did not implement these steps.

The SDK already supports all three. They shipped in 9.1.0 (#301): enableEvents, eventProcessorConfig.eventsApiUrl, getExperimentFlag, trackEvent and trackExposureEvent. So the library code needed no change, and 6a108ea only connects the new steps to the existing public API:

  • Create the SDK client with events enabled: creates a Flagsmith client with enableEvents: true and the events API URL from the runner.
  • Gets the experiment flag: calls getExperimentFlag. Any exposure it records is sent by the SDK's own flush timer. The step does not flush explicitly.
  • Tracks event / tracks an exposure: calls trackEvent / trackExposureEvent with the identifier, value and metadata from the scenario.

I checked it locally against the spec's compose stack at v0.6.0 (Flagsmith 2.287.0, events API, Kafka, warehouse delivery and ClickHouse): 7/7 scenarios pass, and the events are read back from the warehouse. The unit tests also pass (455/455).

I committed with --no-verify. The pre-commit hook regenerates the engine types from Flagsmith main and runs prettier --write .. That would have added unrelated engine-type and CHANGELOG changes to this PR. I ran prettier on the changed file and the full test suite by hand.

🤖 Generated with Claude Code

@renovate
renovate Bot force-pushed the renovate/sdk-spec branch from 6a108ea to 4419850 Compare October 29, 2026 19:53
@renovate renovate Bot changed the title deps: update dependency flagsmith/sdk-spec to v0.6.0 deps: update dependency flagsmith/sdk-spec to v0.7.0 Oct 29, 2026
…c v0.6.0

Spec v0.6.0 adds @events scenarios for getExperimentFlag, trackEvent and
trackExposureEvent, plus a "Create the SDK client with events enabled" step.
The SDK has supported these since 9.1.0, so the steps call the existing
public API.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 6a108ea)
@renovate

renovate Bot commented Oct 30, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@flagsmithsmith

flagsmithsmith Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Superseded by #320, which carries this pull request's implementation work, so that Renovate can keep its bump up to date (it can't rebase a branch others have committed to).

@flagsmithsmith flagsmithsmith Bot closed this Nov 5, 2026
@flagsmithsmith
flagsmithsmith Bot deleted the renovate/sdk-spec branch November 5, 2026 17:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

openhands For the OpenHands agent to pick up sdk-spec Bumps of the Flagsmith SDK behavioural spec

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant