Releases: shipperstack/shippy
1.5.0
Release 1.5.0
Changes since 1.4.2:
- Updated API endpoint URLs according to the changes in shipper.
- Upload exceptions are now treated as errors and styled accordingly when printed to console.
- The server error message has been updated.
- Server compatibility version bumped to 1.8.0.
1.4.2
Release 1.4.2
Changes since 1.4.1:
- Fixed a really, really weird redirection edge-case bug. If the server URL schema was set to HTTP but the web server automatically redirected clients to HTTPS, shippy would issue a GET request instead of a POST request when signing in, which would fail because the login endpoint only accepts POST requests. If this happens, shippy now figures out what is going on and rewrites the server URL while letting the user know.
- Fixed a bug where the login function could occasionally fail if the response received from the server was unexpected.
- General code cleanup
1.4.1
Release 1.4.1
Changes since 1.4.0:
- Added config option
UploadWithoutPrompt
. shippy will automatically upload builds found in the current directory without asking the user for confirmation. - Added command-line option
-y
and--yes
, which is functionally equal to theUploadWithoutPrompt
config above. - Fixed a bug where shippy would create deprecated sections
- shippy now automatically deletes deprecated sections if detected
- Fixed a bug where shippy would use case-insensitive configuration files
- Code cleanup and optimization
1.4.0
Release 1.4.0
Changes since 1.3.19:
- shippy correctly identifies a missing device error
- Added a flag to "disable" the build immediately after uploading (for internal use only)
- Updated invalid configuration message
- Config schema change: the
shipper
section has been removed - Bumped server compat to 1.7.0
With this build, you may be prompted by shippy to sign in again. Delete the ~/.shippy.ini
file before signing in, or edit the file and remove the shipper
section in the configuration.
1.3.19
Release 1.3.19
Changes since 1.3.18:
- shippy checks if the token is valid on start and prompts if the token is invalid.
- Bumped server compatibility version to 1.6.16.
1.3.18
Release 1.3.18
This release is a hotfix for a potential bug introduced in 1.3.17 while backporting shippy to support older Python versions. If shippy hangs when the upload progress gets to 100%, you might want to try re-uploading with 1.3.18.
No other changes since 1.3.17 are present.
1.3.17
Release 1.3.17
Changes since 1.3.16:
- Fixed logic to work in lower Python versions
- shippy now supports all Python 3 versions (starting from 3.5)! Before, the version requirement was Python 3.8 and up. This is a temporary change until all maintainers can update their systems.
1.3.16
Release 1.3.16
Changes since 1.3.15:
- The version requirement has been fixed from 3.5 to 3.8. shippy only runs correctly on versions 3.8 and up.
1.3.15
Release 1.3.15
Changes since 1.3.14:
- shippy now handles connection failures instead of crashing
- shippy no longer crashes on a KeyboardInterrupt (Ctrl-C)
- Bumped server compatibility version to 1.6.12
- Changed and simplified error and warning messages
- General code cleanup
1.3.14
Release 1.3.14
Changes since 1.3.13:
- The option to upload directly to shipper has now been removed. The chunked upload mechanism is the only way to upload to shipper.
- The chunk size is now fixed at 10 MB.
- shippy now shows more details when logging into the server fails.
- An unused debug mechanism has been removed.
- shippy will now exit if the server is out-of-date to prevent any potential errors.
- General code cleanup