Sloth-ci

Latest version: v2.2.1

Safety actively analyzes 630052 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 8

1.2.6

- API: Server: info now returns build status levels too.
- CLI: Colorization is now possible based on any column.
- CLI: info output is now colorized.

1.2.5

- API: info: If the database is unavailable, only build statuses are not returned.
- API: info: The info method didn't work if the database was unavailable. Fixed.
- API: Web: Alias for info added: list.
- API: Web: history, logs: If the database is unavailable, the history and logs methods are still accessible but explicitly return errors.
- Server config: DB path can only point to a file. Previous decision to allow directories led to ambiguity.
- Server config: If the DB path was null (or false, or 0), no apps could be created. Fixed.

1.2.4

- Build: Exec: Support for stream redirection and shell commands added.
- Server config: DB path can now point to a directory; sloth.db will be created automatically.
- Build logging: Trigger events are now logged with level DEBUG, not INFO.
- Util: SqliteHandler: Exception handling on event emitting added.

1.2.3

- Apps with listen points "_" and "x/y" were not logged. Fixed.
- Listen points are used to refer to apps instead of names (i.e. slugs).
- Removed dependency awesome-slugify.
- Sloth: The "name" attribute replaced with "listen_point".

1.2.2

- CLI: info: Alias added: list.

1.2.1

- CLI, API: Logs: If a listen point did not exist, an empty list was returned instead of an error. Fixed.
- Build: Exec: All failed executions were logged with the same "__init__ missing cmd" error. Fixed.
- Build: Exec: Failed actions are logged as error, not critical.
- Build: Exec: If an action failed, its stdout and stderr were not logged. Fixed.
- Build: Exec: In an action fails, its exit code is logged as error. The stdout and stderr are logged as debug, as usual.

Page 4 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.