All Versions
31
Latest Version
Avg Release Cycle
66 days
Latest Release
641 days ago

Changelog History
Page 2

  • v1.1.4 Changes

    July 05, 2019

    Full Changelog

    Closed issues:

    • Valid number range for constrains comparison? #274
    • Strange characters coming through Kinesis stream #267
    • ⬆️ Upgrade to vue-cli 3 for flagr-ui #264
    • 👍 Variant Attachment JSON Support #231

    🔀 Merged pull requests:

  • v1.1.3 Changes

    May 31, 2019

    Full Changelog

    Closed issues:

    • Bulk Evaluation Doesn't Return Variant Information #263
    • Healthcheck Downloading Gzip file? #261

    🔀 Merged pull requests:

    • ➕ Add support for arbitrary JSON in attachments #259 (saary)
    • 🔄 Changed input text to json-editor in flag variant form #258 (yosyad)

  • v1.1.2 Changes

    May 24, 2019

    Full Changelog

    Closed issues:

    • Arbitrary validation rules in feature and variant keys #254
    • 🚀 Release 1.1.1 is missing from Docker Hub #251
    • Fatal Error when Unable to Reach Kafka #244
    • 👌 Support disk files as data source and make flagr read-only under that mode #237
    • 🚀 Release Schedule #211
    • 👌 Support Go Module #201

    🔀 Merged pull requests:

  • v1.1.1 Changes

    April 19, 2019

    Full Changelog

    Implemented enhancements:

    • 👍 Flag Note Support #230

    Closed issues:

    • ⚡️ WebPrefix does not update API_URL #225

    🔀 Merged pull requests:

  • v1.1.0 Changes

    March 20, 2019

    🔄 Changes

    🍱 ❗️#239 introduced a semi-breaking change to the evalResult model. Since fields are no longer required, the zero value (e.g. null, 0) fields are ignored in the final evalResult payload. Old versions of goflagr, rbflagr, and jsflagr are compatible with this change.

    {
  "evalContext": {
    "enableDebug": true,
    "entityContext": {
      "hello": "world"
    },
    "entityID": "a1234",
    "entityType": "report",
    "flagID": 1,
    "flagKey": "kmmcd1nsd6ze56chh"
  },
  "evalDebugLog": {
    "segmentDebugLogs": [
      {
        "msg": "argument: state not found",
        "segmentID": 1
      }
    ]
  },
  "flagID": 1,
  "flagKey": "kmmcd1nsd6ze56chh",
  "flagSnapshotID": 8,
  "segmentID": 1,
  "timestamp": "2019-03-20T00:11:40Z",
  "variantAttachment": null,
  "variantID": null,
  "variantKey": null
}

    becomes

    {
  "evalContext": {
    "enableDebug": true,
    "entityContext": {
      "hello": "world"
    },
    "entityID": "a1234",
    "entityType": "report",
    "flagID": 1,
    "flagKey": "kmmcd1nsd6ze56chh"
  },
  "evalDebugLog": {
    "segmentDebugLogs": [
      {
        "msg": "argument: state not found",
        "segmentID": 1
      }
    ]
  },
  "flagID": 1,
  "flagKey": "kmmcd1nsd6ze56chh",
  "flagSnapshotID": 8,
  "segmentID": 1,
  "timestamp": "2019-03-20T00:11:40Z"
}

  • v1.0.15 Changes

    March 20, 2019

    Full Changelog

    Closed issues:

    • Data Pipeline Format #232
    • Disable enableDebug Propery for Evaluation Transactions #228
    • 🌐 Flagr-UI Cannot Resolve Static Assets when using FLAGR_WEB_PREFIX environment variable #222

    🔀 Merged pull requests:

  • v1.0.14 Changes

    February 22, 2019

    Full Changelog

    Implemented enhancements:

    • 👌 Support Prometheus #196

    Closed issues:

    • Swagger Codegen generated PHP SDK #220
    • Retry DB Connections #207

    🔀 Merged pull requests:

  • v1.0.13 Changes

    January 31, 2019

    Full Changelog

    Closed issues:

    • Empty Arrays Returned for Segments and Variants on GET flags endpoint #199
    • 💻 Granular access control for Flagr UI #195
    • Getting path / was not found on new install #192
    • findFlags not working with key query param #187
    • Flagr segments evaluation should stop if it matches all the constraints in a segment #180
    • Question: Using the JWT Auth #121

    🔀 Merged pull requests:

  • v1.0.12 Changes

    October 23, 2018

    🐛 Bug fixes

    • 🍱 ❗️ Fix segments evaluation logic given 0% rollout segments. #180 #181.

    Note, previously, the evaluation of segments falls through to the next segment for non-rolled out users (e.g. 0% rollout percentage of a segment). The intended behavior is that If the entity context matches the constraints in a segment, it should stop evaluating the following segments. Specifically, for 0% rollout segment, it shouldn't go to the next segments.

  • v1.0.11 Changes

    October 10, 2018

    Full Changelog

    Closed issues:

    • 👌 Support for liveness check in flagr #165
    • 💾 Save Segment button is not clear if it saves the constraints or not #142

    🔀 Merged pull requests: