v0.16.6-ls7

LinuxServer Changes:

Initial Release.

speedtest-tracker Changes:

What's Changed

• [Bug] Fixed chart order by by @alexjustesen in alexjustesen/speedtest-tracker#1206
• [Chore] Verbose lint output by @alexjustesen in alexjustesen/speedtest-tracker#1207
• Release v0.16.6 by @alexjustesen in alexjustesen/speedtest-tracker#1208

Full Changelog: alexjustesen/speedtest-tracker@v0.16.5...v0.16.6

v0.16.5-ls7

LinuxServer Changes:

Initial Release.

speedtest-tracker Changes:

What's Changed

• Milliseconds should be indicated with "ms" and not "Ms" by @Trainax in alexjustesen/speedtest-tracker#1185
• [Bug] Added fix result statuses command by @alexjustesen in alexjustesen/speedtest-tracker#1197
• [Bug] Fixed charts query not ordering by latest by @alexjustesen in alexjustesen/speedtest-tracker#1198
• [Chore] Bit number helpers by @alexjustesen in alexjustesen/speedtest-tracker#1199
• [Feature] Added bit to magnitude helper by @alexjustesen in alexjustesen/speedtest-tracker#1200
• [Bug] Return latest speedtest download and upload in mbits by @alexjustesen in alexjustesen/speedtest-tracker#1201
• Laravel 10.45.0 Shift by @alexjustesen in alexjustesen/speedtest-tracker#1187
• Release v0.16.5 by @alexjustesen in alexjustesen/speedtest-tracker#1202

New Contributors

• @Trainax made their first contribution in alexjustesen/speedtest-tracker#1185

Full Changelog: alexjustesen/speedtest-tracker@v0.16.4...v0.16.5

v0.16.4-ls6

LinuxServer Changes:

Initial Release.

speedtest-tracker Changes:

What's Changed

• [Bug] Capture 1 or true for successful status by @alexjustesen in alexjustesen/speedtest-tracker#1181
• [Bug] Fixed incorrect file size bits calculation by @alexjustesen in alexjustesen/speedtest-tracker#1182
• Release v0.16.4 by @alexjustesen in alexjustesen/speedtest-tracker#1183

Full Changelog: alexjustesen/speedtest-tracker@v0.16.3...v0.16.4

v0.16.3-ls6

LinuxServer Changes:

Initial Release.

speedtest-tracker Changes:

What's Changed

• [Bug] Wrong results value by @alexjustesen in alexjustesen/speedtest-tracker#1160
• [Bug] Download and upload bits should be a nullable int by @alexjustesen in alexjustesen/speedtest-tracker#1170
• [Bug] Don't select null external IP addresses by @alexjustesen in alexjustesen/speedtest-tracker#1172
• Release v0.16.3 by @alexjustesen in alexjustesen/speedtest-tracker#1173

Full Changelog: alexjustesen/speedtest-tracker@v0.16.2...v0.16.3

v0.16.2-ls6

LinuxServer Changes:

Initial Release.

speedtest-tracker Changes:

What's Changed

• Hotfix v0.16.1 by @alexjustesen in alexjustesen/speedtest-tracker#1156
• Hotfix v0.16.2 by @alexjustesen in alexjustesen/speedtest-tracker#1158

Full Changelog: alexjustesen/speedtest-tracker@v0.16.1...v0.16.2

v0.16.1-ls6

LinuxServer Changes:

Initial Release.

speedtest-tracker Changes:

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.

1. Sign in as an admin user and visit the results page.
2. Click "Migrate" at the top of the table and confirm you want to start the data migration.
3. 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.
4. 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.
• Q: Will I lose my old results data?
  • No, even after the data is migrated to the new results table results_bad_json will remain in the database unless you decide to manually drop the table.
• 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

• #1144
• #1149

Full Changelog: alexjustesen/speedtest-tracker@v0.15.5...v0.16.0

v0.16.0-ls6

LinuxServer Changes:

Initial Release.

speedtest-tracker Changes:

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.

1. Sign in as an admin user and visit the results page.
2. Click "Migrate" at the top of the table and confirm you want to start the data migration.
3. 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.
4. 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.
• Q: Will I lose my old results data?
  • No, even after the data is migrated to the new results table results_bad_json will remain in the database unless you decide to manually drop the table.
• 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

• #1144
• #1149

Full Changelog: alexjustesen/speedtest-tracker@v0.15.5...v0.16.0

v0.16.0-ls5

LinuxServer Changes:

Initial Release.

speedtest-tracker Changes:

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.

1. Sign in as an admin user and visit the results page.
2. Click "Migrate" at the top of the table and confirm you want to start the data migration.
3. 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.
4. 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.
• Q: Will I lose my old results data?
  • No, even after the data is migrated to the new results table results_bad_json will remain in the database unless you decide to manually drop the table.
• 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

• #1144
• #1149

Full Changelog: alexjustesen/speedtest-tracker@v0.15.5...v0.16.0

v0.15.5-ls4

LinuxServer Changes:

Initial Release.

speedtest-tracker Changes:

What's Changed

• [Chore] README.md and template updates by @alexjustesen in alexjustesen/speedtest-tracker#1139
• [Bug] Fixed missing version provider namespace by @alexjustesen in alexjustesen/speedtest-tracker#1145
• [Chore] Cache settings values by @alexjustesen in alexjustesen/speedtest-tracker#1146
• Release v0.15.5 by @alexjustesen in alexjustesen/speedtest-tracker#1147

Full Changelog: alexjustesen/speedtest-tracker@v0.15.4...v0.15.5

v0.15.4-ls4

LinuxServer Changes:

Initial Release.

speedtest-tracker Changes:

What's Changed

• [Bug] Fixed testing Telegram notification channel by @alexjustesen in alexjustesen/speedtest-tracker#1130
• Laravel 10.44.0 Shift by @alexjustesen in alexjustesen/speedtest-tracker#1128
• Release v0.15.4 by @alexjustesen in alexjustesen/speedtest-tracker#1132

Full Changelog: alexjustesen/speedtest-tracker@v0.15.3...v0.15.4