[renovate]

This PR contains the following updates:

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

---

Release Notes

Flagsmith/sdk-spec

v0.6.0

Compare Source

What's Changed

• feat: Spec getExperimentFlag, trackEvent and trackExposureEvent by @​gagantrivedi in #​17
• ci: Run Android and Flutter against main in the compatibility matrix by @​khvn26 in #​16
• docs: Implementation flow, CODEOWNERS by @​khvn26 in #​18

New Contributors

• @​gagantrivedi made their first contribution in #​17

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

• feat: Add a Kotlin harness by @​Zaimwa9 in #​9
• feat: Add a Dart harness by @​Zaimwa9 in #​6

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

v0.4.0

Compare Source

What's Changed

• ci: Add the JS client to the compatibility matrix by @​talissoncosta in #​7
• ci: Run the compatibility matrix against merged SDKs' main branches by @​Zaimwa9 in #​8
• feat: Add a Swift harness by @​Zaimwa9 in #​5

New Contributors

• @​talissoncosta made their first contribution in #​7
• @​Zaimwa9 made their first contribution in #​8

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.

[coderabbitai]

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: c2b2dd3c-48d2-4355-8c50-208d77d09395

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

• 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[flagsmithsmith]

Spec v0.6.0 adds @events scenarios: get an experiment flag (with exposure), track an event, and track an exposure event. They also add the Create the SDK client with events enabled step.

This SDK already has these behaviours behind enableEvents (#420 and earlier): getExperimentFlag, trackEvent, trackExposureEvent and eventProcessorConfig.eventsApiUrl. They already have unit tests in test/events.test.ts, test/experiment.test.ts and test/event-processor.test.ts. So no library code change was necessary. The CI failures were only "The SDK does not implement the step".

Changes

• sdk-spec/steps.mts: new Create the SDK client with events enabled step. It sets enableEvents: true and points eventsApiUrl at the spec's events API.
• The experiment flag step identifies the user with their traits, then calls getExperimentFlag.
• The track event and track exposure steps run init() once (the events pipeline starts there), then call trackEvent / trackExposureEvent with the given identifier, value and metadata.

Events are sent on the SDK's own flush timer. The steps do not force a flush.

Verification: I ran the v0.6.0 spec locally against its compose stack (Flagsmith, events API, Kafka, warehouse delivery, ClickHouse) and all 7 scenarios passed. npm run typecheck and npm test (133 tests) also pass.

Review effort: 1/5