fix(deps): update dependency flagsmith to v7 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
flagsmith (source)	^4.0.0 -> ^7.0.0
flagsmith (source)	4.0.0 -> 7.0.2

---

Release Notes

Flagsmith/flagsmith-js-client (flagsmith)

v7.0.2: Version 7.0.2

Compare Source

What's Changed

• fix: Incorrect argument type, interface extension by @​khvn26 in https://github.com/Flagsmith/flagsmith-js-client/pull/261
• fix: Interface extensions are not correct by @​khvn26 in https://github.com/Flagsmith/flagsmith-js-client/pull/266

Full Changelog: Flagsmith/flagsmith-js-client@7.0.1...7.0.2

v7.0.1: Version 7.0.1

Compare Source

Allows flagsmith.setContext({...}) prior to init.

v7.0.0

Compare Source

This is a temporary release that reverts the changes in 6.0.0.

What's Changed

• Bump rollup from 2.78.0 to 2.79.2 by @​dependabot in https://github.com/Flagsmith/flagsmith-js-client/pull/255
• Revert "feat: support multiple environment caching" by @​rolodato in https://github.com/Flagsmith/flagsmith-js-client/pull/258

Full Changelog: Flagsmith/flagsmith-js-client@6.0.0...7.0.0

v6.0.0: Version 6.0.0 - Adjust cache keys to be unique per environment

Compare Source

Closes #​201. The local storage keys for the SDK cache are now unique for each environment. This is being released as a breaking change because, upon upgrading to this version, the cache will be missed the first time due to the previous key ('BULLET_TRAIN_DB') being ignored

Thank you very much for the great PR @​oluizcarvalho 🚀

v5.0.0: Version 5.0.0 - Support context, transient identities and traits

Compare Source

Transient traits

This release supports the concept of transient traits, setting this will mean the trait is not stored within Flagsmith and evaluated just in that request.

You can define a trait as transient like so:

setTraits({bar:{value:123, transient: true}})
setTraits({foo:"1", bar:{value:123, transient: true}})
flagsmith.init({
  traits: {foo:"1", bar:{value:123, transient: true}}
})

Contexts and transient identities

This release also deprecates the above calls in favour of setting context. Context allows you to set information as a single object which we may extend in future more easily. We suggest migrating to this soon.

You can set a partial context and it will merge with the one provided during SDK init.

Currently, the full context object looks like this:

flagsmith.setContext({
  {
    environment: {apiKey: "<your environment API key>"},
    identifier: "unique-user-id",
    traits:     {foo:"1", bar:{value:123, transient: true}},
    transient:  false
  }
})

---

Configuration

📅 Schedule: 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 is behind base branch, 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.