Batou-ext

Latest version: v2.4.28

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

Scan your dependencies

Page 2 of 5

2.4.23

- Fix using multiple DeploymentTrash Component on a single host breaking the Nix rebuild, especially across different deployments to the same machine.
This was because the values for the IOPS read and write Limits in the Systemd serviceConfig attribute set were defined as strings (which cannot be merged unless identical) instead of lists (which can always be merged).

2.4.22

- Allow to configure the name of the `.nix` file created by `batou_ext.file.DeploymentTrash`.

2.4.21

- Fix interactive version select.

- Change the releaser defaults to actually release

2.4.20

- Correctness fix for `jenkins set-version`: if a tag is resolved, make sure it's _always_
resolved to the rev of the tagged commit (instead of the tag's rev) or fail hard to avoid
incorrect revs.

- Improve documentation of `batou_ext.file.DeploymentTrash`

2.4.19

- make the DeploymentTrash's trash directory configurable and output a potentially helpful message on OSErrors which could indicate that the trash directory and the directory that is being trashed are on different devices

2.4.18

- nixos.NixOSModule: Mark generated context file as sensitive (Fixes 167)

- add an env argument for the `Run` component to support running commands with specific environment variables

- The component `batou_ext.python.FixELFRunPath` now uses a patched version of patchelf to make sure that the
dynamic libraries don't get larger per deploy.

When a certain threshold is exceeded, Python will fail to import these.

If the component got regularly executed in deployments, you may want to consider recreating
the virtualenv once.

Page 2 of 5

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.