Releases: Betterment/test_track_rails_client
v8.2.1
What's Changed
- Bump nokogiri from 1.18.4 to 1.18.8 by @dependabot in #153
- update vendored testtrack-cli to 1.7.0 by @kelvin-acosta in #157
New Contributors
- @kelvin-acosta made their first contribution in #157
Full Changelog: v8.2.0...v8.2.1
Contributors
Assets 2
v8.2.0
What's Changed
- Bump uri from 1.0.2 to 1.0.3 by @dependabot in #150
- Bump rack from 3.1.8 to 3.1.12 by @dependabot in #148
- Bump nokogiri from 1.18.2 to 1.18.3 by @dependabot in #146
- Avoid booting Rails to generate timestamp by @rzane in #152
- Bump nokogiri from 1.18.3 to 1.18.4 by @dependabot in #151
Full Changelog: v8.1.1...v8.2.0
Contributors
Assets 2
v8.1.1
Contributors
Assets 2
v8.1.0
What's Changed
Full Changelog: v8.0.0...v8.1.0
Contributors
Assets 2
v8.0.0
What's Changed
- feat: Add Rails 7.1 - 8 support by @argvniyx-enroute in #141
New Contributors
- @argvniyx-enroute made their first contribution in #141
Full Changelog: v7.1.2...v8.0.0
Contributors
Assets 2
v4.0.2
v4.0.0
- Upgraded to TestTrack JS Client 2.0
- Rewritten in TypeScript (Betterment/test_track_js_client#29)
- Migrated from JQuery to axios and native Promises (Betterment/test_track_js_client#22)
- Improved safety during migrations to prevent retired splits from impacting running apps (#97)
- Added a new Session type to improve performance during background work (#84)
- Added support for Rails 6 (#96)
Raise a normalized error class for unrecoverable errors
If you use an error alerting tool like Sentry or Airbrake to identify software quality problems, you can now filter out TestTrack::UnrecoverableConnectivityErrors from your software quality alerting, and instead treat these errors as an error-rate operational alert indicating a problem connecting to your TestTrack server instance.
Application-wide feature flags
This release includes the concept of an ApplicationIdentity, and allows apps to configure an app_name. This enables consumers to easily access app-wide feature flags, that are useful in cases that aren't necessarily tied to an end user (e.g., a background job, or toggling between different versions of an external API that your app is consuming). This allows you to decouple deployment from release without the added granularity of a gradual rollout in cases where you don't need it.
4.0 alpha4
Fix bug with AnalyticsEvent module resolution preventing events from shipping