Releases: alexjustesen/speedtest-tracker
v0.16.4
What's Changed
- [Bug] Capture 1 or true for successful status by @alexjustesen in #1181
- [Bug] Fixed incorrect file size bits calculation by @alexjustesen in #1182
- Release v0.16.4 by @alexjustesen in #1183
Full Changelog: v0.16.3...v0.16.4
v0.16.3
What's Changed
- [Bug] Wrong results value by @alexjustesen in #1160
- [Bug] Download and upload bits should be a nullable int by @alexjustesen in #1170
- [Bug] Don't select null external IP addresses by @alexjustesen in #1172
- Release v0.16.3 by @alexjustesen in #1173
Full Changelog: v0.16.2...v0.16.3
v0.16.2
What's Changed
- Hotfix v0.16.1 by @alexjustesen in #1156
- Hotfix v0.16.2 by @alexjustesen in #1158
Full Changelog: v0.16.1...v0.16.2
v0.16.0 (Data Quality - Action Required!)
Important
v0.16.0
includes a breaking change that requires user action for existing installs. Make sure to follow the steps below to migrate your result data!
This release fixes a data quality issue (#812) that has existed since day-1. Result responses stored in data
column where incorrectly formatted which caused extra steps and some messy code throughout the application. This release will copy your existing results
table to a new results_bad_json
table for safe keeping and deploy new DDL for a fresh results
table.
Data Migration
If you have existing results data you can follow the steps below to migrate and fix your data.
- Sign in as an admin user and visit the results page.
- Click "Migrate" at the top of the table and confirm you want to start the data migration.
- The migration will be processed by a queue worker behind the scenes, you'll receive notifications at the start and end of the data processing. This can take a couple of minutes depending how much data you have.
- Once completed you'll need to add your schedule for speedtests back under General settings.
FAQ
- Q: Where the F*** did my data go?
- It was copied to a new table called
results_bad_json
for safe keeping.
- It was copied to a new table called
- Q: Will I lose my old results data?
- No, even after the data is migrated to the new
results
tableresults_bad_json
will remain in the database unless you decide to manually drop the table.
- No, even after the data is migrated to the new
- Q: Why were my scheduled speedtests disabled?
- This fix is so important it requires your attention, once you've confirmed a successful data migration you can enable your scheduled speedtests again.
Additional Changes
Full Changelog: v0.15.5...v0.16.0
v0.15.5
What's Changed
- [Chore] README.md and template updates by @alexjustesen in #1139
- [Bug] Fixed missing version provider namespace by @alexjustesen in #1145
- [Chore] Cache settings values by @alexjustesen in #1146
- Release v0.15.5 by @alexjustesen in #1147
Full Changelog: v0.15.4...v0.15.5
v0.15.4
What's Changed
- [Bug] Fixed testing Telegram notification channel by @alexjustesen in #1130
- Laravel 10.44.0 Shift by @alexjustesen in #1128
- Release v0.15.4 by @alexjustesen in #1132
Full Changelog: v0.15.3...v0.15.4
v0.15.3
What's Changed
- [Chore] Removed schedule for new installs by @alexjustesen in #1119
- [Feature] A better favicon by @alexjustesen in #1124
- Release v0.15.3 by @alexjustesen in #1125
Full Changelog: v0.15.2...v0.15.3
v0.15.2 (Hotfix)
v0.15.1
What's Changed
- [Chore] Refactored getting Ookla speedtest servers by @alexjustesen in #1109
- [Bug] Timezone in API returns by @DidierMetral in #1070
- [Feature] Silently send notifications for Telegram by @alexjustesen in #1110
- Release v0.15.1 by @alexjustesen in #1112
New Contributors
- @DidierMetral made their first contribution in #1070
Full Changelog: v0.15.0...v0.15.1
v0.15.0 (Webhook Notifications!)
What's Changed
- [Chore] Added one time operations package by @alexjustesen in #1100
- [Feature] Add webhook notifications by @alexjustesen in #1103
- [Chore] Refactor notification channel tests by @alexjustesen in #1104
- [Chore] Refactored get jitter data method by @alexjustesen in #1105
- Release v0.15.0 by @alexjustesen in #1106
Full Changelog: v0.14.7...v0.15.0