Skip to content

Releases: Flagsmith/flagsmith

Version 2.7.4

28 Jun 10:02
4da498c
Compare
Choose a tag to compare
  • Fix build pipelines by using correct version of chrome in E2E tests

Version 2.7.3

25 Jun 12:42
18e9c96
Compare
Choose a tag to compare

Fixed Github action for production deployment

Version 2.7.2

25 Jun 11:22
637591f
Compare
Choose a tag to compare

Fixes #143 with #147

Version 2.7.1

24 May 09:28
Compare
Choose a tag to compare
  • Upgrade django debug toolbar based on vulnerability
  • Add new environment variable to prevent unknown logins when self hosting

Version 2.7.0

24 May 09:27
Compare
Choose a tag to compare

Version 2.6.0

19 Apr 10:38
Compare
Choose a tag to compare
  • Combine Feature Flags and Remote Config
  • Dark mode
  • Formatter for remote config supporting xml, json, toml and yaml
  • Fix Segment override incorrect date
  • Add sorting to identity feature list
  • Enable SDK analytics based on FLAGSMITH_ANALYTICS env var
  • Configurable butterbar
  • Show segment descriptions
  • New integrations
    • Mixpanel
    • Heap Analytics
    • New Relic

Breaking changes:

  • Segment overrides use new API

Version 2.5.0

20 Jan 20:07
Compare
Choose a tag to compare
  • Add invite via link functionality
  • More third party integration work

2.4.0 - Initial Flagsmith Release

07 Dec 13:15
Compare
Choose a tag to compare

This release is the first under our new brand, Flagsmith.

The rebrand comes with no breaking changes, mainly just a refactor to urls and wording, however we have built several new features and bug fixes since our last release:

  • If your api is using influx, we now show usage data in a graph format
    image
  • New look and feel
  • Ability to bulk enable / disable all segment overrides and user overrides for a flag
    image
  • Sensible page size for the users page
  • Improved E2E stability
  • Integration page, this page is almost fully managed by remote config. It will allow users t enhance Flagsmith with your favourite tools. We currently support data dog and will shortly support amplitude.
    image

The remote config to use this is as follows:

integrations:

["data_dog"]
integration_data
{
    "perEnvironment": false,
    "image": "https://xyz",
    "fields": [
      {
        "key": "base_url",
        "label": "Base URL"
      },
      {
        "key": "api_key",
        "label": "API Key"
      }
    ],
    "tags": [
      "logging"
    ],
    "title": "Data dog",
    "description": "Sends events to Data dog for when flags are created, updated and removed. Logs are tagged with the environment they came from e.g. production."
}

Version 2.3.0

09 Nov 10:43
Compare
Choose a tag to compare

We've added a bunch of new features and bug fixes.

  • You can now tag flags with user-defined tags. You can use these tags to manage flags and organise them.
  • Beta release of both Data Dog and Amplitude integrations.
  • You can now set multiple traits in a single call
  • For a given feature, show which Identities have it individually overridden
  • When viewing an Identity, show the segments and test whether the identity is a member of each segment

Version 2.2.0

13 Aug 09:13
Compare
Choose a tag to compare

Flags that are defined with Segment overrides are now based on an Environment level, as opposed to a Project level. So you can now define Segment overrides differently between Environments.