Skip to content

Releases: Unleash/unleash-edge

unleash-edge v17.0.0

15 Jan 19:06
eb43027
Compare
Choose a tag to compare

Unleash Edge v17.0.0

Chore

  • update rust crate shadow-rs to 0.26.0
  • update rust crate testcontainers-modules to 0.3.1
  • update rust crate actix-http to 3.5.1

New Features

  • Use Version-headers to decide where to post metrics
    • feat: Edge now dynamically posts to correct upstream metrics endpoint
  • added client authenticated bulk metrics
    • filters metrics posted by environment accessible by token

Bug Fixes

  • update rust crate clap to 4.4.16
  • update rust crate utoipa-swagger-ui to v6
  • update rust crate actix-cors to 0.7.0
  • update rust crate utoipa to 4.2.0
  • update rust-futures monorepo to 0.3.30
  • update rust crate opentelemetry_sdk to 0.21.2
  • update rust crate serde to 1.0.195
  • update rust crate actix-web to 4.4.1
  • update rust crate redis to 0.24.0
  • update rust crate tokio to 1.35.1
  • update rust crate serde_json to 1.0.111
  • update rust crate ahash to 0.8.7
  • update rust crate clap to 4.4.14
  • update rust crate anyhow to 1.0.79
  • update rust crate async-trait to 0.1.77

Other

  • Added version header to client register response

Commit Statistics

Commit Details

view details

unleash-edge v16.1.0

20 Dec 11:06
b50787f
Compare
Choose a tag to compare

Chore

  • update rust crate test-case to 3.3.1

New Features

  • token-header override
    --token-header <TOKEN_HEADER>
    Token header to use for both edge authorization and communication with the upstream server [env: TOKEN_HEADER=] [default: Authorization]

    This is useful in complex deployment scenarios where proxies are using the Authorization header.

Bug Fixes

  • update rust crate serde to 1.0.193

  • update rust crate reqwest to 0.11.23

  • Do not remove features cache if upstream goes away

    • fix: Do not remove features cache if upstream goes away

    If upstream goes away, edge should remain durable and keep the features
    it has gotten for the tokens. Now use backoff to save time.

Commit Statistics

  • 6 commits contributed to the release over the course of 4 calendar days.
  • 19 days passed between releases.
  • 5 commits were understood as conventional.
  • 5 unique issues were worked on: #345, #346, #360, #362, #363

Commit Details

view details

unleash-edge v16.0.6

30 Nov 11:42
85e1867
Compare
Choose a tag to compare

Chore

  • update rust crate testcontainers-modules to 0.2.0
  • Bump to opentelemetry 0.21

New Features

  • obey http status responses. backoff when 429 or 50x

Bug Fixes

  • bump deps to fix issue serializing
  • readd http metrics
    After upgrading opentelemetry we lost our http metrics on our prometheus
    metrics dump due to a different call setup for getting it to work. This
    PR again sets up our configured meter provider to be used for all
    prometheus metrics. Which allows us to have our custom middleware work
    again.
  • use chrono durations and make jitter random 0..5 seconds instead of 0..5000 ms

Commit Statistics

  • 6 commits contributed to the release over the course of 6 calendar days.
  • 6 days passed between releases.
  • 6 commits were understood as conventional.
  • 5 unique issues were worked on: #339, #347, #350, #351, #354

Commit Details

view details
  • #339
    • obey http status responses. backoff when 429 or 50x (33a511d)
  • #347
    • update rust crate testcontainers-modules to 0.2.0 (71a7a2d)
  • #350
    • use chrono durations and make jitter random 0..5 seconds instead of 0..5000 ms (3618299)
  • #351
  • #354
    • bump deps to fix issue serializing (0a30141)
  • Uncategorized
    • Bump to opentelemetry 0.21 (4106baa)

unleash-edge v16.0.5

30 Nov 11:29
22afcb3
Compare
Choose a tag to compare

Chore

  • Bump to opentelemetry 0.21

New Features

  • obey http status responses. backoff when 429 or 50x

Bug Fixes

  • readd http metrics
    After upgrading opentelemetry we lost our http metrics on our prometheus
    metrics dump due to a different call setup for getting it to work. This
    PR again sets up our configured meter provider to be used for all
    prometheus metrics. Which allows us to have our custom middleware work
    again.
  • use chrono durations and make jitter random 0..5 seconds instead of 0..5000 ms

Commit Statistics

  • 8 commits contributed to the release over the course of 6 calendar days.
  • 6 days passed between releases.
  • 4 commits were understood as conventional.
  • 3 unique issues were worked on: #339, #350, #351

Commit Details

view details
  • #339
    • obey http status responses. backoff when 429 or 50x (33a511d)
  • #350
    • use chrono durations and make jitter random 0..5 seconds instead of 0..5000 ms (3618299)
  • #351
  • Uncategorized

unleash-edge v16.0.4

23 Nov 13:22
5b88605
Compare
Choose a tag to compare

Bug Fixes

Commit Statistics

  • 1 commit contributed to the release.
  • 9 days passed between releases.
  • 1 commit was understood as conventional.
  • 1 unique issue was worked on: #342

Commit Details

view details

unleash-edge v16.0.3

13 Nov 14:28
dfab30d
Compare
Choose a tag to compare

Bug Fixes

  • upgrades yggdrasil to 0.8.0, this fixes an issue with constraints not parsing correctly with free quotes

Commit Statistics

  • 1 commit contributed to the release.
  • 4 days passed between releases.
  • 1 commit was understood as conventional.
  • 1 unique issue was worked on: #337

Commit Details

view details
  • #337
    • upgrades yggdrasil to 0.8.0, this fixes an issue with constraints not parsing correctly with free quotes (7a9c453)

unleash-edge v16.0.2

09 Nov 09:52
0b1380a
Compare
Choose a tag to compare

Bug Fixes

  • Wildcard token refreshing.

    • fix: Wildcard token refreshing.

    Previously our refreshing algorithm assumed that we always had at least
    one project with an explicit name for deciding what to keep. When in
    reality we could have a wildcard token (*) for updating. This means that
    we should just return the update as our new set of data for this token.

    Added another test with a wildcard token to verify that we do indeed
    only keep the update.

    In addition, added a filter for unique feature names to what we're
    keeping to avoid mixing multiple features of the same name.

Commit Statistics

  • 1 commit contributed to the release.
  • 7 days passed between releases.
  • 1 commit was understood as conventional.
  • 1 unique issue was worked on: #330

Commit Details

view details

unleash-edge v16.0.1

01 Nov 13:43
f3c4c62
Compare
Choose a tag to compare

Chore

  • prepare for 16.0.1 release

Bug Fixes

  • Handle archived/deleted projects
    Previously, our cache refresh algorithm assumed that the response from
    upstream contained all projects we wanted to do updates to. Wayfair
    correctly reported this breaking their opportunity to archive/delete
    projects, since the cache would still contain deleted projects.

    This patch updates Edge to use the projects the token has access to
    decide whether or not to keep the elements in cache.

    New flow:

    1. Fetch projects from token
    2. Filter out all features belonging to these projects
    3. Extend remaining list with update from response
    4. Return extended list.

Commit Statistics

  • 2 commits contributed to the release.
  • 2 commits were understood as conventional.
  • 1 unique issue was worked on: #324

Commit Details

view details
  • #324
    • Handle archived/deleted projects (5ddd1f5)
  • Uncategorized
    • prepare for 16.0.1 release (fc5ded0)

unleash-edge v16.0.0

01 Nov 12:14
fe761a2
Compare
Choose a tag to compare

Chore

  • prepare for release

New Features

  • Add support for setting log format at startup

Commit Statistics

  • 2 commits contributed to the release.
  • 1 day passed between releases.
  • 2 commits were understood as conventional.
  • 1 unique issue was worked on: #322

Commit Details

view details
  • #322
    • Add support for setting log format at startup (d27b81d)
  • Uncategorized

unleash-edge v15.0.0

30 Oct 14:40
6f56a77
Compare
Choose a tag to compare

Chore

  • bump yggdrasil version
  • remove dotenv and bump ahash to a non-yanked version
  • dependencies bump
  • bump renovate bot suggestions
  • Start work upgrading to opentelemetry 0.20

Documentation

  • Update dependency pointer to 14.0.0

New Features

  • make edge log bad request information from upstream

Commit Statistics

  • 8 commits contributed to the release over the course of 14 calendar days.
  • 14 days passed between releases.
  • 7 commits were understood as conventional.
  • 3 unique issues were worked on: #292, #313, #319

Commit Details

view details
  • #292
    • Start work upgrading to opentelemetry 0.20 (30958a1)
  • #313
    • Make edge log bad request information from upstream (e77ea18)
  • #319
  • Uncategorized
    • Update dependency pointer to 14.0.0 (8279ec0)
    • Release unleash-edge v14.0.0 (e0cdb5c)
    • Remove dotenv and bump ahash to a non-yanked version (0bda1cf)
    • Dependencies bump (0c6b33a)
    • Bump renovate bot suggestions (1b4277e)