Agent Control v1.25.0

New features

• Linux: added Debian 13 (trixie) as a supported/published platform.
• Linux: removed the legacy on-host folder migration pre-v1.2.0 from newrelic-agent-control-cli
• Variants support has been removed in favor of the "governance" flow server side
• Regex-based remote config validation has been removed in favor of the "governance" flow server side.

Bug fixes

• On-host: fixed a spurious error-level log "cannot forward agent control event" emitted on every clean shutdown; the status server bridge now exits only via an explicit stop signal, closed channels are silently disabled rather than causing an exit, and publisher lifetimes are extended to keep channels open until the stop signal fires.
• Linux: uninstall.sh now uses apt-get purge instead of apt-get remove, preventing a dpkg state inconsistency that caused reinstallation to fail, the service could not start because the systemd-env.conf conffile was not recreated by the package manager.
• Windows: the uninstall script now warns instead of silently succeeding when the install or runtime-data directory cannot be removed (e.g. Windows Explorer has it open), and preserves the script itself so it can be re-run once the lock is released.
• On-host: filesystem entries under filesystem:/shared_filesystem: are now written to disk in alphabetical order and fsynced after each write, making the write order deterministic.
• On-host: self-update no longer deletes the downloaded package's binary when replacing the running binary, fixing rollback and same-version reinstall after a self-update.
• On-host: fixed a spurious Error reading the log directory/files: No such file or directory message printed to stderr the first time Agent Control's or a sub-agent's log directory is created.
• On-host: executable output and lifecycle logs are no longer misleadingly tagged with the start_agent span for the entire lifetime of agent processes and supervisors, they carry the explicit fields instead.
• On exit, the process-terminated log line (success or error) is no longer dropped from the log file: it used to be emitted after the file logger had already shut down, so it only ever reached journalctl/stderr.

Security updates

• Update rustls
• Updated rust crate reqwest to 0.13.5
• Updated rust crate encoding_rs to 0.8.41
• Updated alpine/helm to v4.3.0
• Updated rust crate toml to 1.1.6
• Updated rust crate clap to 4.6.7
• Updated rust crate jsonwebtoken to 11.1.0
• Updated rust crate opamp-client to v0.1.0
• Updated rust crate cfg-if to 1.0.5
• Updated rust crate syn to 3.0.6
• Updated rust crate serde-saphyr to 1.3.0
• Updated rust crate nr-auth to v0.5.3

For a detailed description of changes, see the release notes.