Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency flagsmith to v7 #1082

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 19, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
flagsmith (source) ^4.0.0 -> ^7.0.0 age adoption passing confidence
flagsmith (source) 4.0.0 -> 7.0.1 age adoption passing confidence

Release Notes

Flagsmith/flagsmith-js-client (flagsmith)

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

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.

@renovate renovate bot requested a review from a team as a code owner October 19, 2024 04:41
@renovate renovate bot added the renovate label Oct 19, 2024
@renovate renovate bot force-pushed the renovate/flagsmith-7.x branch 8 times, most recently from edf40df to 4a67c1f Compare October 23, 2024 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants