Skip to content

9.0.0

Latest

Choose a tag to compare

@OpenVoxProjectBot OpenVoxProjectBot released this 11 Nov 22:11
· 7 commits to main since this release
Immutable release. Only release title and notes can be modified.
9.0.0
d33a138

OpenBolt 9.0.0 follows 5.6.0 and is the first release of the OpenBolt 9 series. The version number moves from 5 to 9 so that OpenBolt and OpenVox share a major version. There are no OpenBolt 6, 7, or 8 releases.

Highlights

  • OpenBolt is built on OpenVox 9. The packages bundle OpenVox 9.3.0, Ruby 4.0.9, and OpenSSL 3.5.9. The gem requires OpenVox 9 and Ruby 3.4 or newer.
  • The Choria transport can upload and download files through the new overlookinfra-mcollective_agent_file_transfer agent, and its results and errors now match the other transports in many more cases.
  • Plans that run other plans many levels deep no longer fail with SystemStackError.
  • --targets accepts JSON, so the JSON output of one bolt command can be the target list of the next one.
  • Values that OpenBolt passes to PowerShell can no longer end the quoted string that contains them.
  • The Windows package is built with MSYS2. Fedora 45 is added, and Amazon Linux 2, Debian 11, Fedora 42, and Ubuntu 25.04 are removed. The list of supported platforms aligns with OpenVox 9.

Upgrading from OpenBolt 5.x

  1. Use the openvox9 repositories. OpenBolt 9 packages are published in the openvox9 repositories and download directories, next to the OpenVox 9 agent. OpenBolt 5.x packages were published in openvox8. Install the openvox9-release package for your platform from https://yum.voxpupuli.org/ or https://apt.voxpupuli.org/ (note that openvox8-release and openvox9-release can't be installed side-by-side on Debian/Ubuntu platforms at the moment, but we're working on it), then upgrade the openbolt package. macOS disk images are at https://downloads.voxpupuli.org/mac/openvox9/ and the Windows installer is at https://downloads.voxpupuli.org/windows/openvox9/.
  2. Check your platform. See Platforms under Packaging below.
  3. Install extra gems again. Gems that you installed for OpenBolt's Ruby have to be installed again, because gem directories are named after the Ruby version. /opt/puppetlabs/bolt/lib/ruby/gems/3.2.0 becomes /opt/puppetlabs/bolt/lib/ruby/gems/4.0.0, and gems installed with --user-install move from a 3.2.0 to a 4.0.0 directory in the same way.
  4. Check Ruby code against Ruby 4.0. Ruby code that OpenBolt loads runs on Ruby 4.0 instead of 3.2. That covers the plan functions, data types, and plugins in your modules, and Ruby tasks that run on localhost with the bundled Ruby. If that code requires a gem that the package no longer includes, install the gem. See Removed gems under Packaging below.
  5. Review plans and manifests against OpenVox 9. Plans, apply blocks, and bolt apply are compiled with OpenVox 9 instead of 8, and the bundled OpenFact moves from 5 to 6. Changes to the language and its functions apply to them. See the OpenVox 9 release notes and the OpenVox 8 to 9 upgrade guide.
  6. Decide which agent apply_prep installs. See the apply_prep entry under Breaking changes below.
  7. Choria users, read the Choria section. Several error kinds changed, and the directory that the tmpdir option names now has to exist on the targets. See the Choria transport section below.

Breaking changes

  • OpenVox 9 is required for the gem The gem depends on openvox ~> 9.0, where 5.x depended on openvox ~> 8.0. (#332). Note: OpenVox 9 is not required on your targets.

  • Ruby 3.4 is the minimum for the gem. The gem's required Ruby version moves from 3.2 to 3.4. The packages bundle Ruby 4.0.9. (#340)

  • apply_prep installs the OpenVox 9 agent by default. On a target without an agent, apply_prep installs openvox-agent with the openvox_bootstrap::install task. The bundled openvox_bootstrap module moves from 1.4.0 to 1.8.0, and its default collection changed from openvox8 to openvox9. A Linux target that already has an agent keeps it. On a Windows target, the task installs the collection's agent version even when another version is installed, so a Windows target with an OpenVox 8 agent is upgraded to OpenVox 9 unless the target declares the puppet-agent feature in the inventory. apply_prep never runs the install task on targets with that feature. To keep installing the OpenVox 8 agent, set the collection in the puppet_library plugin hook in bolt-project.yaml or bolt-defaults.yaml:

    plugin-hooks:
      puppet_library:
        plugin: openvox_bootstrap
        collection: openvox8
  • Fewer platforms. Packages are no longer built for Amazon Linux 2, Debian 11, Fedora 42, and Ubuntu 25.04.

  • Fewer bundled gems. The packages no longer include the orchestrator client, the Hiera 3 gem, WEBrick, and the optional Faraday adapters. See Removed gems under Packaging below.

  • Plans can be nested 1000 levels deep at most. A plan that runs itself without a condition that stops it fails with Plans cannot be nested more than 1000 levels deep when it reaches that depth. _catch_errors and catch_errors() don't catch this error. (#372)

  • Choria transport results changed. See Changed behavior in the Choria transport section below.

New features

  • JSON target lists. --targets accepts a JSON array of target names, or a JSON result object with an items array, as printed by --format json. OpenBolt takes the target of every item, whatever the item's status. This makes the output of one command usable as the target list of the next one. The JSON can be given inline, from a file with @<file>, or on stdin with -. (#281)

    bolt command run 'systemctl is-active sshd' --targets linux --format json | bolt command run 'uptime' --targets -
  • File upload and download over Choria. See the Choria transport section below. (#358)

  • sudo-rs. OpenBolt recognizes the run-as errors of sudo-rs, which words them differently from GNU sudo. A user without sudo permission and a rejected sudo password get OpenBolt's usual error messages on targets that use sudo-rs. (#341)

Fixes

  • Nested plans no longer overflow the stack. A plan that runs a plan that runs another plan, as the patching plans in issue #181 do, could fail with SystemStackError. Every run_plan call now runs its plan on a new Fiber with an empty stack. (#372)
  • Plan runs end about half a second sooner. OpenBolt slept for 0.5 seconds after the last part of a plan had finished. (#372)
  • Apply on OpenVox 9 agents. Applying a catalog on a target with an OpenVox 9 agent no longer puts a catalog name mismatch error at the top of the report logs. OpenBolt names the node after the catalog for the apply. (#341)
  • SSH connect timeouts on Ruby 4.0. Ruby 4.0 raises a different error class for a connect timeout. OpenBolt reports it as Timeout after <seconds> seconds connecting to <target>, the same message as on older Ruby versions. (#332)
  • The tmpdir error names the directory. The message is now Could not make tmpdir <path>, followed by the error output. (#341)
  • Spinner. The first character of a line printed right after the spinner stopped could appear to be missing. (#315)
  • Documentation links and names. Help output, guides, and error messages link to docs.openvoxproject.org instead of the dead pup.pt short links. The generated reference pages call the product OpenBolt, and their tables and option descriptions render correctly. (#279, #280, #353, #354)

Choria transport

User guide: https://docs.openvoxproject.org/openbolt/latest/choria-transport.html

New

  • Upload and download. bolt file upload, bolt file download, and the upload_file and download_file plan functions work over the Choria transport. In 5.6.0 they failed with bolt/choria-unsupported-operation. Transfers go through the file_transfer agent, version 1.0.0 or later, on the targets. The agent's module, overlookinfra-mcollective_agent_file_transfer, also has to be applied with client => true on the host where OpenBolt runs, because it installs the client library that OpenBolt uses. (#358)
  • Transfer options. file-transfer-timeout is the wait for each file transfer request in seconds, default 300. message-data-size is the file content per Choria message in KiB, default 512. upload-batch-size is the number of targets that one upload chunk is published to at a time, default 256. (#358)
  • Scripts and task files of any size through the shell agent. Files go to the targets in chunks. Before, a script, task, or task file over about 7.5 KB, or under 3 KB for a Windows target, could not be sent. (#380)
  • PowerShell input method. A task whose metadata sets input_method to powershell gets its parameters on Windows targets when it runs through the shell agent. (#376)
  • Tasks with lib and scripts files through the bolt_tasks agent. OpenBolt asks the server for these files at the paths where the server provides them. Before, the server answered 404 and the task could not run. (#381)
  • Choria targets behind the remote transport. A Choria target can be the run-on target of a remote target. (#382)
  • Ruby 4.0. The gem depends on choria-mcorpc-support ~> 2.28. Release 2.28.0 works on Ruby 4.0. (#357)

Changed behavior

  • The tmpdir directory has to exist. The transport no longer creates the directory that the tmpdir option names, like the SSH transport. A target without it fails with Could not make tmpdir. (#382)
  • A failed task has the same error for every agent. A task that exits non-zero through the bolt_tasks agent is reported with kind puppetlabs.tasks/task-error, like it is with the other transports and with the shell agent. Before, the kind was choria.tasks/task-error. (#382)
  • Failed preparation steps are file errors. When a target can't make the tmpdir, copy a file, or make a script or task executable, the error has kind puppetlabs.tasks/task_file_error and a message that starts with Could not. Before, the kind was bolt/choria-operation-failed. (#382, #383)
  • Discovery errors say what happened. A target that doesn't answer agent discovery gets bolt/choria-no-response, and a target that answers without an agent list gets bolt/choria-missing-data. Before, both got bolt/choria-agent-not-available. A target whose discovery call failed, for example because an action policy denied it, gets that error. (#378)
  • Denied and aborted requests are RPC errors. A reply with status code 1 from the shell or rpcutil agent, such as an action policy's You are not authorized to call this agent or action, is reported as an RPC error with the agent's message. A task that can't be started is reported with kind bolt/choria-task-start-failed. (#349)
  • Upload results name the destination as given, like the other transports. (#382)

Fixed

  • Commands and scripts see the variables from _env_vars. Before, a reference such as $VAR in a command came out empty, and scripts didn't get the variables. (#376)
  • On Windows targets, scripts without environment variables run, commands with environment variables run unchanged, and environment variable values and script arguments that aren't strings no longer fail the whole batch. (#376)
  • A target without a suitable task implementation, such as a Windows node for a shell-only task, gets its own error. The other targets in the batch run the task. (#377)
  • A malformed discovery reply affects only the target that sent it. (#378)
  • OpenBolt removes the shell agent's job directory once it has the job's output, on targets whose cleanup option is on. Before, each node's job list grew with every job until its reply passed the broker's 1 MiB message limit, and every later command on that node failed with no response. (#380)
  • Job output is fetched in groups of 200 targets, so replies stay under the broker's message limit when thousands of targets finish together. (#380)
  • An rpc-timeout of 5 is applied. A Windows target's tmpdir is removed when OpenBolt runs on Linux. The tmpdir is removed when a run is interrupted during the uploads. run_task_with reports a target that stays silent in discovery once, without waiting out the timeout again for each such target. (#349)

Security

Hardening

  • PowerShell quoting. PowerShell reads the curly single quotes U+2018 to U+201B as single quotes. A value that contained one ended the single-quoted string that OpenBolt had built, and the rest of the value was read as PowerShell. Environment variable values and .ps1 script arguments had the same problem with a line that starts with '@. OpenBolt now doubles all 5 quote characters and passes these values as base64. This affects the WinRM transport, the SSH transport with login-shell: powershell, the local, Docker, and Podman transports when OpenBolt runs on Windows, and Windows targets of the Choria transport. (#379)
  • Choria job records. Script arguments, environment variable values, and task parameters, Sensitive ones included, are no longer written to the shell agent's job record on the node or returned in the agent's job list. (#380)
  • Choria tmpdir on Windows. The tmpdir on a Windows target is open only to the account that the agent runs as and to the Administrators group. Before, it inherited the permissions of its parent directory. (#380)

Security issues resolved in bundled components

Identifier CVSS 3.1 Score Resolved By
CVE-2026-54904 7.5 pkg:gem/concurrent-ruby@1.3.8
CVE-2026-54905 5.5 pkg:gem/concurrent-ruby@1.3.8
CVE-2026-54906 N/A pkg:gem/concurrent-ruby@1.3.8
CVE-2026-54297 7.5 pkg:gem/faraday@2.15.1
CVE-2026-45363 7.4 pkg:gem/jwt@2.10.3
CVE-2026-47242 N/A pkg:gem/net-imap@0.6.4.1
CVE-2026-47241 N/A pkg:gem/net-imap@0.6.4.1
CVE-2026-47240 N/A pkg:gem/net-imap@0.6.4.1
CVE-2026-85396 7.5 pkg:gem/rubyzip@3.7.0
CVE-2026-86140 7.8 pkg:github/gnome/libxml2@2.15.4
CVE-2026-86138 7.8 pkg:github/gnome/libxml2@2.15.4
CVE-2026-11979 7.8 pkg:github/gnome/libxml2@2.15.4
CVE-2026-86144 7.8 pkg:github/gnome/libxml2@2.15.4
CVE-2026-86139 7.8 pkg:github/gnome/libxml2@2.15.4
CVE-2026-86142 7.8 pkg:github/gnome/libxml2@2.15.4
CVE-2026-86143 7.3 pkg:github/gnome/libxml2@2.15.4
CVE-2026-86137 6.1 pkg:github/gnome/libxml2@2.15.4
CVE-2026-86141 3.3 pkg:github/gnome/libxml2@2.15.4
CVE-2026-75803 9.1 pkg:github/openssl/openssl@3.5.9
CVE-2026-84782 8.2 pkg:github/openssl/openssl@3.5.9
CVE-2026-63076 7.5 pkg:github/openssl/openssl@3.5.9
CVE-2026-63072 7.5 pkg:github/openssl/openssl@3.5.9
CVE-2026-54874 7.5 pkg:github/openssl/openssl@3.5.9
CVE-2026-63074 5.9 pkg:github/openssl/openssl@3.5.9
CVE-2026-35189 5.3 pkg:github/openssl/openssl@3.5.9
CVE-2026-75805 5.3 pkg:github/openssl/openssl@3.5.9
CVE-2026-75806 5.3 pkg:github/openssl/openssl@3.5.9
CVE-2026-77696 3.7 pkg:github/openssl/openssl@3.5.9
CVE-2026-54872 3.7 pkg:github/openssl/openssl@3.5.9

Packaging

Platforms

Packages are built for these platforms:

  • Amazon Linux 2023 (x86_64, aarch64)
  • Debian 12 (amd64, arm64) and 13 (amd64, arm64, armhf)
  • Enterprise Linux 8, 9, and 10 (x86_64, aarch64)
  • Fedora 43, 44, and 45 (x86_64, aarch64)
  • SLES 15 (x86_64) and 16 (x86_64, aarch64)
  • Ubuntu 22.04 (amd64, arm64), 24.04 and 26.04 (amd64, arm64, armhf)
  • macOS 13 and later (Intel and Apple silicon)
  • Microsoft Windows (x64)

Removed since 5.6.0: Amazon Linux 2, Debian 11, Fedora 42, and Ubuntu 25.04.
New since 5.6.0: Fedora 45 (#373).

The full list of platforms will always track https://github.com/OpenVoxProject/shared-actions/blob/main/platforms.json#L3

The Windows package is built with the MSYS2 UCRT64 toolchain instead of Cygwin, like the OpenVox 9 agent. (#332)

Components

The packages are built on puppet-runtime 2026.11.06.1. 5.6.0 was built on 2026.06.10.1. https://github.com/OpenVoxProject/shared-actions/blob/main/platforms.json#L3

Component 5.6.0 9.0.0
OpenVox 8.28.0 9.3.0
OpenFact 5.6.1 6.2.1
Ruby 3.2.11 4.0.9
OpenSSL 3.0.21 3.5.9
puppet-ca-bundle 1.1.0 2.0.0
augeas 1.14.1 1.15.0
libffi 3.5.2 3.8.0
libxml2 2.15.3 2.15.4
ruby-shadow 2.5.1 voxpupuli fork, commit bc7752a9
addressable 2.9.0 2.9.2
aws-eventstream 1.4.0 1.4.1
aws-partitions 1.1259.0 1.1301.0
aws-sdk-core 3.251.0 3.264.0
aws-sdk-ec2 1.622.0 1.664.0
choria-mcorpc-support 2.26.5 2.28.0
colored2 4.0.3 4.1.0
concurrent-ruby 1.3.6 1.3.8
faraday 2.14.2 2.15.1
faraday-follow_redirects 0.3.0 0.5.0
faraday-net_http 3.4.4 3.5.0
fast_gettext 2.4.0 4.1.1
httpclient 2.9.0 2.10.0
jwt 2.10.2 2.10.3
multi_json 1.19.1 1.21.2
net-scp 4.1.0 4.2.1
net-ssh 7.3.2 7.3.8
nori 2.7.1 2.9.1
openvox-strings 7.1.0 7.2.0
puppet-resource_api 2.0.0 2.0.1
rubyntlm 0.6.5 0.6.8
rubyzip 2.4.1 3.7.0
sys-filesystem 1.5.5 1.6.0
unicode-display_width 3.2.0 3.3.0
unicode-emoji 4.2.0 4.3.0
windows_error 0.1.5 0.1.6
winrm 2.3.9 2.4.2
winrm-fs 1.3.5 1.3.7
yard 0.9.44 0.9.45

The Ruby standard library and its default gems moved with Ruby. The components that are not in the table, r10k 5.0.3 and hiera-eyaml 5.0.1 among them, keep their versions.

Removed gems

These gems are no longer in the packages:

  • orchestrator_client and its dependencies net-http-persistent and connection_pool. The pcp transport that used them was removed in 5.1.0, though may be re-added in a future release.
  • hiera, the Hiera 3 gem.
  • webrick.
  • The optional Faraday adapters and what they depend on: faraday-em_http, faraday-em_synchrony, faraday-excon, faraday-httpclient, faraday-multipart, faraday-net_http_persistent, faraday-patron, faraday-rack, faraday-retry, em-http-request, em-socksify, eventmachine, cookiejar, http_parser.rb, excon, patron, and multipart-post. faraday-net_http and faraday-follow_redirects remain.

base64 and net-http are no longer separate components, because Ruby 4.0 ships them.

To add a gem back for your own code, run /opt/puppetlabs/bolt/bin/gem install --user-install <GEM>, or "C:/Program Files/Puppet Labs/Bolt/bin/gem.bat" install --user-install <GEM> on Windows.

Bundled modules

Every bundled module is updated. 7 of them move to a new major version: service, package, puppet_conf, reboot, scheduled_task, stdlib, and ruby_task_helper. The changelogs of service 4.0.0, package 4.0.0, puppet_conf 3.0.0, and reboot 6.0.0 name dropped Puppet 7 support as their breaking change. Check the changelogs on the Puppet Forge if your plans depend on one of these modules.

Module 5.6.0 9.0.0
puppet-openvox_bootstrap 1.4.0 1.8.0
puppetlabs-apt 11.3.1 11.4.1
puppetlabs-augeas_core 2.0.1 2.1.0
puppetlabs-aws_inventory 0.7.0 0.9.0
puppetlabs-azure_inventory 0.5.1 0.6.0
puppetlabs-bash_task_helper 2.2.0 2.3.0
puppetlabs-cron_core 2.0.2 2.1.0
puppetlabs-facts 1.7.0 1.8.1
puppetlabs-gcloud_inventory 0.3.1 0.4.0
puppetlabs-host_core 2.0.1 2.1.0
puppetlabs-http_request 0.3.2 0.4.0
puppetlabs-inifile 6.4.0 6.6.0
puppetlabs-mount_core 2.0.1 2.1.0
puppetlabs-package 3.1.0 4.0.0
puppetlabs-pkcs7 0.1.2 0.2.0
puppetlabs-powershell 6.1.0 6.2.0
puppetlabs-powershell_task_helper 0.1.0 0.2.0
puppetlabs-puppet_conf 2.1.0 3.0.0
puppetlabs-pwshlib 2.0.1 2.1.1
puppetlabs-python_task_helper 0.6.0 0.7.0
puppetlabs-reboot 5.1.0 6.1.0
puppetlabs-ruby_plugin_helper 0.3.0 0.4.0
puppetlabs-ruby_task_helper 0.6.1 1.1.0
puppetlabs-scheduled_task 4.0.3 5.1.0
puppetlabs-secure_env_vars 0.2.0 0.3.0
puppetlabs-selinux_core 2.0.1 2.1.0
puppetlabs-service 3.1.0 4.0.0
puppetlabs-sshkeys_core 3.0.1 3.1.0
puppetlabs-stdlib 9.7.0 10.1.1
puppetlabs-terraform 0.7.2 0.8.0
puppetlabs-vault 0.4.1 0.5.0
puppetlabs-yaml 0.2.0 0.3.0
puppetlabs-yumrepo_core 3.0.1 3.1.0
puppetlabs-zfs_core 2.0.1 2.1.0
puppetlabs-zone_core 2.0.2 2.1.0

What's Changed

Breaking Changes 🛠

New Features 🎉

  • Allow to pass a JSON array/object as a target list to CLI by @jay7x in #281
  • Choria transport fixes and cleanup by @nmburgan in #349
  • Add upload and download to the Choria transport through the file_transfer agent by @nmburgan in #358
  • Add Choria transport acceptance testing by @nmburgan in #384
  • Add Fedora 45 to packaging platforms by @Sharpie in #373

Dependency Updates ⬆️

  • Update dependency puppetlabs-inifile to v6.4.1 by @renovate[bot] in #260
  • Update dependency puppetlabs-aws_inventory to v0.8.0 by @renovate[bot] in #257
  • Update dependency puppetlabs-apt to v11.3.2 by @renovate[bot] in #261
  • Update dependency puppetlabs-ruby_task_helper to v1 by @renovate[bot] in #92
  • Pin bindata gem dependency to < 3.0 by @Sharpie in #273
  • Update dependency puppetlabs-sshkeys_core to v3.0.2 by @renovate[bot] in #283
  • Update dependency puppetlabs-scheduled_task to v5 by @renovate[bot] in #269
  • Update dependency puppetlabs-cron_core to v2.0.3 by @renovate[bot] in #286
  • Update dependency puppetlabs-scheduled_task to v5.1.0 by @renovate[bot] in #294
  • Update dependency puppetlabs-inifile to v6.5.0 by @renovate[bot] in #289
  • Update dependency puppetlabs-puppet_conf to v3 by @renovate[bot] in #293
  • Update dependency puppetlabs-reboot to v6 by @renovate[bot] in #288
  • Update dependency puppetlabs-pwshlib to v2.1.1 by @renovate[bot] in #295
  • Update dependency puppetlabs-package to v4 by @renovate[bot] in #290
  • Update dependency puppetlabs-service to v4 by @renovate[bot] in #291
  • Update dependency puppetlabs-apt to v11.4.0 by @renovate[bot] in #296
  • Update dependency puppetlabs-powershell to v6.2.0 by @renovate[bot] in #297
  • Update dependency puppetlabs-stdlib to v10 by @renovate[bot] in #299
  • Update dependency puppetlabs-azure_inventory to v0.6.0 by @renovate[bot] in #301
  • Update dependency puppetlabs-bash_task_helper to v2.3.0 by @renovate[bot] in #302
  • Update dependency puppetlabs-facts to v1.8.0 by @renovate[bot] in #303
  • Update dependency puppetlabs-gcloud_inventory to v0.4.0 by @renovate[bot] in #304
  • Update dependency puppetlabs-pkcs7 to v0.2.0 by @renovate[bot] in #306
  • Update dependency puppetlabs-powershell_task_helper to v0.2.0 by @renovate[bot] in #307
  • Update dependency puppetlabs-terraform to v0.8.0 by @renovate[bot] in #312
  • Update dependency puppetlabs-http_request to v0.4.0 by @renovate[bot] in #305
  • Update dependency puppetlabs-ruby_plugin_helper to v0.4.0 by @renovate[bot] in #309
  • Update dependency puppetlabs-ruby_task_helper to v1.1.0 by @renovate[bot] in #310
  • Update dependency puppetlabs-yaml to v0.3.0 by @renovate[bot] in #314
  • Update dependency puppetlabs-aws_inventory to v0.9.0 by @renovate[bot] in #300
  • Update dependency puppetlabs-python_task_helper to v0.7.0 by @renovate[bot] in #308
  • Update dependency puppetlabs-secure_env_vars to v0.3.0 by @renovate[bot] in #311
  • Update dependency puppetlabs-vault to v0.5.0 by @renovate[bot] in #313
  • Update dependency puppetlabs-facts to v1.8.1 by @renovate[bot] in #319
  • Update dependency puppet-openvox_bootstrap to v1.5.0 by @renovate[bot] in #318
  • Update dependency puppetlabs-cron_core to v2.1.0 by @renovate[bot] in #321
  • Update dependency puppetlabs-mount_core to v2.1.0 by @renovate[bot] in #323
  • Update dependency puppetlabs-yumrepo_core to v3.1.0 by @renovate[bot] in #326
  • Update dependency puppetlabs-augeas_core to v2.1.0 by @renovate[bot] in #320
  • Update dependency puppetlabs-zfs_core to v2.1.0 by @renovate[bot] in #327
  • Update dependency puppetlabs-zone_core to v2.1.0 by @renovate[bot] in #328
  • Update dependency puppetlabs-sshkeys_core to v3.1.0 by @renovate[bot] in #325
  • Update dependency puppetlabs-selinux_core to v2.1.0 by @renovate[bot] in #324
  • Update dependency puppetlabs-host_core to v2.1.0 by @renovate[bot] in #322
  • Update dependency puppetlabs-inifile to v6.6.0 by @renovate[bot] in #350
  • Update dependency puppetlabs-reboot to v6.1.0 by @renovate[bot] in #351
  • Update dependency puppetlabs-apt to v11.4.1 by @renovate[bot] in #347
  • Update dependency puppetlabs-stdlib to v10.1.1 by @renovate[bot] in #348
  • Update dependency puppet-openvox_bootstrap to v1.7.0 by @renovate[bot] in #355
  • Update dependency puppet-openvox_bootstrap to v1.8.0 by @renovate[bot] in #366

Other Changes

  • Clarify description of workflow "branch" input by @Sharpie in #268
  • Replace dead pup.pt short links with docs.openvoxproject.org URLs by @miharp in #279
  • Remove setup.ps1 Cygwin setup script by @Sharpie in #284
  • Promote puppet-runtime 2026.09.02.1 by @OpenVoxProjectBot in #292
  • Fix spinner related first character 'truncation' by @davids-uta-edu in #315
  • Changes for OpenBolt 9 by @nmburgan in #332
  • Promote puppet-runtime 2026.10.15.1 by @OpenVoxProjectBot in #333
  • Put the prerelease label in the PowerShell manifest's PSData by @nmburgan in #335
  • Revert "Release 9.0.0-rc1" by @nmburgan in #337
  • Update build.yml to set default branch to main by @nmburgan in #336
  • Temporarily use git repo for choria-mcorpc-support by @nmburgan in #339
  • Remove openssl gem in Gemfile by @nmburgan in #338
  • Update CI test coverage by @nmburgan in #341
  • Fix broken tables and missing descriptions in generated reference pages by @miharp in #354
  • Call the product OpenBolt in the generated reference docs by @miharp in #353
  • Use relative links where the text lands in the docs collection by @miharp in #280
  • Depend on choria-mcorpc-support 2.28 by @nmburgan in #357
  • Promote puppet-runtime 2026.11.04.1 by @OpenVoxProjectBot in #359
  • Promote puppet-runtime 2026.11.04.2 by @OpenVoxProjectBot in #360
  • Remove packaging configuration for Ubuntu 25.04 by @Sharpie in #361
  • Install the file_transfer agent from the Forge in the testing guide by @nmburgan in #364
  • Run the test stack on OpenVox Server and OpenVoxDB images by @nmburgan in #365
  • Complete the Puppetfile in the Choria testing guide by @nmburgan in #368
  • Fix incorrect platform string in debian-13-armhf.rb by @nmburgan in #370
  • Run each nested plan on its own Fiber by @nmburgan in #372
  • Run the sudo-tagged local tests in a Linux container by @nmburgan in #367
  • Promote puppet-runtime 2026.11.06.1 into main by @OpenVoxProjectBot in #375
  • Fix env vars and Windows commands in the Choria shell agent path by @nmburgan in #376
  • Fail only the Choria targets without a matching task implementation by @nmburgan in #377
  • Report why Choria agent discovery failed for each target by @nmburgan in #378
  • Double every PowerShell single quote character and pass values as base64 by @nmburgan in #379
  • Remove Choria shell job records and keep arguments out of them by @nmburgan in #380
  • Ask the server for a task's lib and scripts files where it serves them by @nmburgan in #381
  • Add single-target methods to the Choria transport and match 3 results of the other transports by @nmburgan in #382
  • Report a failed Choria preparation step like the other transports by @nmburgan in #383
  • Remove packaging configuration for Fedora 42 by @Sharpie in #374

New Contributors

Full Changelog: 5.6.0...9.0.0