Releases: shipperstack/shipper
1.8.2
Release 1.8.2
Changes since 1.8.1:
- Removed the v2 all builds API endpoint due to lack of use.
- Fixed a bug where the download count for the past 24 hours API endpoint would use the incorrect time range.
- Fixed a race condition when incrementing the download counters.
- Removed the v2 updater device API endpoint as it was not being used.
- Fixed an incorrect API request type being used. Because of this change, shippy 1.5.1 and up are compatible with this release. Previous versions will fail to change the build enable status.
- Fixed a server error bug that would manifest from operating on a field too early, if the field was blank in the request.
- Lot of code cleanup and optimizations
- Massive improvements to testing suite. shipper is now more resilient against crashes and bugs thanks to the increased test coverage!
1.8.1
Release 1.8.1
Changes since 1.8.0:
- Fixed a display bug in the admin panel where "Statisticss" had an additional 's'
- Download count API endpoints have been added to query download counts for the last 24 hours, last 7 days, and last 31 days
- Disabled web-based view for DRF (Django REST Framework). Responses should now show as plain JSON instead of a web page, and POSTing directly from the browser has now been disabled.
- The updater API now uses DRF instead of Django to return responses, for both v1 and v2 endpoints.
- The updater API now returns a 400 if the supplied variant name is invalid.
- The updater API now returns a more descriptive 404 message.
- Reduced throttling rates for anonymous users. The previous rate was too strict and could inconvenience users refreshing.
- Fixed a bug with nginx passing the incorrect HOST header to shipper.
- Fixed a bug with Django generating the redirect URL for the API.
- General code cleanup
1.8.0
Release 1.8.0
This release contains a database migration AND several important API endpoint changes. Please be careful when upgrading!
Changes since 1.7.4:
- The admin page for builds now shows the download count as a column.
- A database model to track daily downloads has been added.
- All API endpoints have been moved to the API app and refactored. shippy 1.5.0 is required to interface with shipper 1.8.0.
- General code cleanup
- Updated library dependencies (humanize, sentry-sdk)
1.7.4
Release 1.7.4
This is an emergency patch release to prevent the audit log from filling up with download counter changes. No other changes since 1.7.3 have been added.
1.7.3
Release 1.7.3
This release contains a database migration. Please follow the upgrade instructions in the wiki!
Changes since 1.7.2:
- Fixed a counting bug with statistics calculation for administrators
- shipper now alerts users if debug mode is enabled to make sure users do not accidentally use testing environments
- The API throttling rates have been adjusted to reduce server load
- The build model now has a download counter
- Added an API endpoint to increase the download counter
- General code cleanup
1.7.2
Release 1.7.2
This release contains important security patches. Please update as soon as possible.
Changes since 1.7.1:
- Dependencies updated:
- Django from 3.2.4 to 3.2.5
- django-celery-beat from 2.2.0 to 2.2.1
- django-celery-results from 2.1.0 to 2.2.0
- Added an "audit log" to log changes across all models
1.7.1
Release 1.7.1
Changes since 1.7.0:
- Added management command to de-initialize a "full" user account
- Fixed a bug with setting the enabled field of builds to true for new uploads
- Added enabled field as a column and filter option in the admin panel for build objects
1.7.0
Release 1.7.0
This update changes the database schema. Remember to migrate and follow the upgrade procedures in the wiki!
Changes since 1.6.16:
- shipper now signs out the user if the password has been changed
- Updated token invalidation message on the password change screen
- Removed the redirect to dashboard button on sign-up screen
- The admin panel now allows filtering of devices by status
- The admin panel now allows filtering of mirror servers by enabled/downloadable status
- Added a command to initialize a "full" user - i.e. user with access to all devices. This is useful if you want to create a build bot user that can upload to all devices. Note that this user must already exist within the system!
- Build objects can now be "enabled" and "disabled." When build objects are disabled, they are hidden from users and the API endpoints.
- The build ID is now exposed to maintainers on a successful upload.
- Added a maintainer endpoint to enable/disable builds on upload
- Library dependency updates
1.6.16
Release 1.6.16
Changes since 1.6.15:
- shipper now invalidates the authentication token if the password has been changed.
- Added an endpoint for shippy to check token validity.
- Fixed a bug where the admin password change template would get overridden with the custom password change template.
1.6.15
Release 1.6.15
Changes since 1.6.14:
- The
hasBuilds
field has been removed from the v2 all builds API endpoint since it is redundant. Only devices with builds are shown in the endpoint. - Fixed a bug with the codename detection where invalid file names could result in an invalid codename being detected.
- The internal statistics command now shows more information to the administrator.
- Fixed a bug with the template order being processed incorrectly.
- The navbar in the maintainer section has been cleaned up.
- The shippy notice in the upload menu has been removed, since we're planning to add chunked upload support to the web UI.
- Many miscellaneous improvements and fixes
- Code cleanup
- Added more test cases