[renovate]

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

• feat: Support environment-level flag dependency by @​emyller in #​19

New Contributors

• @​emyller made their first contribution in #​19

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

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: bde15ea1-90af-4db3-8ae7-ccac9cedfa0b

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: 7f0e5a49-9177-4a83-9b25-308297f11309

Commits

Reviewing files that changed from the base of the PR and between 3e778a5 and f5f3801.

Files selected for processing: 2

• .github/workflows/sdk-spec.yml
• sdk-spec/Steps.java

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 spec workflow reference and spec-ref change from v0.3.0 to v0.6.0. The Java spec steps add a client configuration that enables events and sets the API and events URLs. They also add steps to retrieve an experiment flag and track events and exposure events, forwarding the supplied metadata.

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

Merge Risk: Minimal · previous review f5f38

The updated spec integration has no established merge-blocking risk.

- [ ] 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.}

[codspeed]

Merging this PR will not alter performance

✅ 15 untouched benchmarks

---

_{Comparing renovate/sdk-spec (0c48af8) with main (3e778a5)}

[flagsmithsmith]

Spec v0.6.0 adds @events scenarios: getting an experiment flag, tracking an event, and tracking a $flag_exposure event. CI was red because sdk-spec/Steps.java implemented only 3 of the 7 steps.

This SDK already has these features, added in #226: FlagsmithClient.getExperimentFlag, trackEvent, trackExposureEvent, and FlagsmithConfig.withEnableEvents / eventsUri. So no library change was needed. f5f3801 wires the four new steps to those methods:

• Create the SDK client with events enabled: builds the client with FlagsmithConfig.newBuilder().baseUri(apiUrl).withEnableEvents(true).eventsUri(eventsUrl). baseUri has to be set on the config, because withConfiguration replaces whatever config withApiUrl set.
• gets the experiment flag: getExperimentFlag(feature, identifier, traits), returned as a one-flag list.
• tracks event and tracks an exposure: trackEvent(...) and trackExposureEvent(...), with the spec's value and metadata passed through unchanged. The SDK's own event buffer delivers them on its flush timer.

Verified locally:

• The full v0.6.0 spec passes 7/7 against the spec's compose stack (Flagsmith 2.287.0, events API, Kafka, warehouse delivery, ClickHouse).
• mvn verify passes: checkstyle, and 481 tests.

[renovate]

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.