Nusex

Latest version: v1.3.0

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

Scan your dependencies

Page 3 of 5

1.1.0

Additions

- Mult-language support, both in the API and the CLI
- Support for Rust dynamic templates
- Logging and verbose mode (`nusex -v ...` or `nusex --version ...`)

Changes

- More powerful blueprint interface, allowing for regexes and inheritance from generic blueprints
- Removal of `nsx` command

Fixes

- Fix issue caused by `pathlib` in older Python versions
- Fix oversight in `rename` method that allowed templates to be renamed to invalid names

1.0.2

**Fixes:**

- Fixed various issues related to renaming profiles and templates

1.0.1

**Bug fixes:**

- The user now cannot delete the currently selected template
- Migrating now sets the last update check correctly
- Downloading now sets the last update check correctly

1.0.0

**IT'S FINALLY HERE!**

The number of changes between v0.4 and v1.0 are far too extensive to list here, but you can see the progress by reading the release notes for the development versions and checking the [migration guide](https://nusex.readthedocs.io/en/latest/info/migrate.html).

Hope you enjoy the new stuff! (:

1.0.0rc2

This will be the last release before v1.0.0 stable! Just gotta get the docs sorted, and fix any bugs that may or may not still be present.

**New things:**

- The update checker and auto update options are now good to go
- The user config now uses the date instead of a version number for the last update check (this shouldn't break older configs as there are things in place to default the relevant variables)
- There's a new `config` command to allow you to update your user config (though only one option is available)
- Profiles can now be renamed and deleted

**Fixes:**

- Prevent the user from being able to select a non-existant profile

1.0.0rc1

nusex is now in release candidate territory! That means there's only slight changes to come before the v1 is fully released.

There should be **no more breaking changes**. Anything that needs breaking I'll have to work around until v2.

**New stuff:**

- The `delete` command
- The `rename` command
- The `list` command

**To-dos before v1 stable:**

- Update docs, cos they're currently not complete
- Activate some config settings. Some are dormant (and one will have to stay dormant for now), but others, such as the `auto_update` will be active in rc2

Page 3 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.