Releases: Unleash/unleash-edge
Releases · Unleash/unleash-edge
unleash-edge v19.6.2
Chore
- prepare for 19.6.2 patch release
- raise error message when failing to validate tokens and url has url postfix
- prepare for release
- Utoipa 5, Yggdrasil 0.13.4
-
chore(deps): Bump to utoipa 5
-
fix: update cargo-dist to 0.23
-
Bug Fixes
- added error if no tokens are valid when starting in strict mode
- update rust crate iter_tools to 0.24.0
- update rust crate unleash-yggdrasil to 0.14.0
Commit Statistics
- 8 commits contributed to the release.
- 40 days passed between releases.
- 7 commits were understood as conventional.
- 5 unique issues were worked on: #571, #580, #581, #587, #588
Commit Details
view details
- #571
- Utoipa 5, Yggdrasil 0.13.4 (dc6f169)
- #580
- Update rust crate unleash-yggdrasil to 0.14.0 (0efccf0)
- #581
- Update rust crate iter_tools to 0.24.0 (7ba15a9)
- #587
- Added error if no tokens are valid when starting in strict mode (92c85db)
- #588
- Raise error message when failing to validate tokens and url has url postfix (f0df427)
- Uncategorized
unleash-edge-v19.6.1
What's Changed
- chore(deps): Utoipa 5, Yggdrasil 0.13.4 by @chriswk in #571
- fix(deps): update rust crate tokio to v1.41.0 by @renovate in #573
Full Changelog: unleash-edge-v19.6.0...unleash-edge-v19.6.1
Contributors
chriswk and renovate
Assets 16
unleash-edge v19.6.0
Chore
- prepare for release
New Features
-
internal-backstage endpoints are disableable.
Sensitive endpoint (tokens, features, metricsbatch, metrics) can now all
be turned off with separate flags -
flush metrics on clean shutdown
-
Support prometheus remote write protocol for metrics
-
fix: make sure to post correct registry to vm
-
feat: Add support for remote writing prometheus
-
Other
- remove request tracing
Originally we wanted to support OpenTelemetry for tracing, but we no
longer support setting up an OTEL_COLLECTOR, so removing the request
tracer seems sensible
Commit Statistics
- 5 commits contributed to the release.
- 6 days passed between releases.
- 5 commits were understood as conventional.
- 4 unique issues were worked on: #548, #563, #564, #565
Commit Details
unleash-edge v19.5.1
Bug Fixes
- frontend all endpoints now accept context correctly
- remove bucket creation in s3 persister
- prefix unused vars
Commit Statistics
- 3 commits contributed to the release over the course of 2 calendar days.
- 5 days passed between releases.
- 3 commits were understood as conventional.
- 2 unique issues were worked on: #557, #558
Commit Details
unleash-edge v19.5.0
Chore
- Prepare 19.5.0 release
- Remove unnecessary dbg! macros
- bump cargo dependencies
Documentation
-
Add client-tokens and frontend-tokens chapter to offline mode
- Update server/readme
New Features
- s3 persister
Commit Statistics
- 5 commits contributed to the release.
- 12 days passed between releases.
- 5 commits were understood as conventional.
- 2 unique issues were worked on: #536, #542
Commit Details
unleash-edge v19.4.1
Chore
- bump dependency status link
- update dependency link in README
- dependency maintenance
- update log message
- Upgrade to actix 4.9, tokio 1.40, opentelemetry 0.24
-
chore: bump to actix 4.9 and upgrade packages
-
chore: Upgrade Opentelemetry to 0.24
-
New Features
- added support for client and frontend tokens to offline mode.
-
feat: added support for client and frontend tokens to offline mode. Assume tokens passed in --tokens are client tokens
-
clean up tests to use the new interface
-
fix: Added client and frontend tokens to constructor
-
Updated CLI docs
-
- added feature_toggle_usage_total counter
- verbose error for instance urls with api suffix
Bug Fixes
- allow offline mode to have either tokens or client-tokens set
- Update to explicitly type RedisError.
Work around for Rust 2024 implementing Never type (!)
Commit Statistics
- 12 commits contributed to the release.
- 18 days passed between releases.
- 10 commits were understood as conventional.
- 7 unique issues were worked on: #465, #512, #513, #520, #531, #532, #535
Commit Details
view details
- #465
- Added support for client and frontend tokens to offline mode. (b48604c)
- #512
- Update instruction to refer to docker command not tag (113d1ef)
- #513
- Upgrade to actix 4.9, tokio 1.40, opentelemetry 0.24 (715e8e9)
- #520
- Verbose error for instance urls with api suffix (10d3854)
- #531
- Update to explicitly type RedisError. (797fc49)
- #532
- Added feature_toggle_usage_total counter (00aabbe)
- #535
- Dependency maintenance (9e3d251)
- Uncategorized
unleash-edge-v19.4.0
What's Changed
- Upgrade to actix 4.9, tokio 1.40, opentelemetry 0.24 by @chriswk in #513
- Update instruction to refer to docker command not tag by @melindafekete in #512
- chore(deps): update toshimaru/auto-author-assign action to v2.1.1 by @renovate in #397
- docs: add additional details for debugging by @gastonfournier in #517
- Fix formatting to avoid JSX rendering bug by @melindafekete in #518
- fix(deps): update rust crate dashmap to v6.1.0 by @renovate in #529
- fix: Update to explicitly type RedisError. by @chriswk in #531
- chore: add arm64 build for linux as well by @chriswk in #530
- feat: verbose error for instance urls with api suffix by @Tymek in #520
- feat: added feature_toggle_usage_total counter by @chriswk in #532
- feat: added support for client and frontend tokens to offline mode. by @chriswk in #465
- chore: dependency maintenance by @chriswk in #535
Full Changelog: unleash-edge-v19.3.1...unleash-edge-v19.4.0
Contributors
chriswk, gastonfournier, and 3 other contributors
Assets 16
unleash-edge v19.3.1
Chore
- remove warnings as a result of new rust version
-
chore: disable tarpaulin warnings
-
chore: remove unneeded sync-middleware feature
-
- update rust crate shadow-rs to 0.30.0
Documentation
- update dependency pointer to planned release
- Restructure readme
- Add prometheus endpoint
- Reformat binary list
- Add code formatting for shell commands
Bug Fixes
-
added PostContext handling properties and context as nested variants
- chore: add some test cases to cement behavior
Commit Statistics
- 5 commits contributed to the release.
- 5 commits were understood as conventional.
- 3 unique issues were worked on: #494, #507, #510
Commit Details
view details
unleash-edge v19.3.0
Chore
- prepare 19.3.0
- make clippy warnings into failures
New Features
- upgrade types library, unfortunately this does two things - adds new optional metrics data and adds backwards compatability for impression_data
Bug Fixes
- use app name as appname header
- trim tokens when parsing
- fix: trim tokens when parsing
Other
- Dependency maintenance
Commit Statistics
- 6 commits contributed to the release over the course of 9 calendar days.
- 9 days passed between releases.
- 6 commits were understood as conventional.
- 5 unique issues were worked on: #479, #489, #490, #491, #492
Commit Details
view details
- #479
- Dependency maintenance (fa2f974)
- #489
- Upgrade types library, unfortunately this does two things - adds new optional metrics data and adds backwards compatability for impression_data (9795c7c)
- #490
- Use app name as appname header (c1a3acd)
- #491
- Make clippy warnings into failures (8e57fe3)
- #492
- Trim tokens when parsing (5281287)
- Uncategorized
- Prepare 19.3.0 (7854e28)
unleash-edge v19.2.1
Chore
- prepare for release
Documentation
-
strict and dynamic mode
Bug Fixes
-
add timeout for redis read and write ops.
Previously, if you gave us a redis url that was valid, but used the
wrong protocol (so rediss when connecting to insecure, or redis when
connecting to secure), operations against Redis got stuck. This PR adds
a timeout setting (setting it to default of 2000 ms, but configurable).This does add time when url is completely invalid (i.e. there's nothing
listening), but it prevents the client from getting stuck indefinitely
if something answers, but redis can't get an answer.
Commit Statistics
- 4 commits contributed to the release over the course of 7 calendar days.
- 8 days passed between releases.
- 3 commits were understood as conventional.
- 2 unique issues were worked on: #477, #478