github nzymedefense/nzyme 2.0.0-alpha.16

latest release: 2.0.0-alpha.17
pre-release8 months ago

Release blog post: https://www.nzyme.org/blog/project/2025/04/10/release-v200-alpha-16

Breaking Changes

  • New migrate command must be executed after update. See Upgrade Procedure below.
  • New required nzyme-tap configuration option
[protocols.uav_remote_id]
pipeline_size = 1024

Important Changes

  • The data retention configuration is now tenant-based and can be found on the "Database" page of each tenant. Before this, it was globally defined under "System". An automatic migration applies the previous global configuration to each tenant during upgrade.

Other notes

  • There are new system event types that trigger when MFA was disabled for a user.

Upgrade Procedure

nzyme-node

If you are upgrading from a previous version, you can simply run dpkg -i on the new release package, execute database migrations and restart the nzyme-node service. Always upgrade nzyme-node before nzyme-tap unless instructed otherwise.

Debian-based systems:

sudo systemctl stop nzyme
sudo dpkg -i nzyme-node_[version].deb
sudo nzyme --migrate-database
sudo systemctl daemon-reload
sudo systemctl start nzyme

nzyme-tap

If you are upgrading from a previous version, you can simply run dpkg -i on the new release package and restart the nzyme-tap service. Always upgrade nzyme-node before nzyme-tap unless instructed otherwise.

Debian-based systems:

sudo systemctl stop nzyme-tap
sudo dpkg -i nzyme-tap_[version].deb
sudo systemctl daemon-reload
sudo systemctl start nzyme-tap

Don't miss a new nzyme release

NewReleases is sending notifications on new releases.