Build Update Policy: Automated or manual?

[reneleonhardt]

What is the update policy for new builds, are they triggered manually?
https://github.com/chef/bento/blob/main/.github/workflows/pkr-bld-virtualbox-arm64.yml

Since the last build 202508.03.0 there have been new releases, for example Ubuntu 24.04.3 and 22.04.5, VirtualBox 7.2 and Parallels Desktop 26.

https://documentation.ubuntu.com/project/release-team/list-of-releases/
https://www.virtualbox.org/wiki/Changelog
https://kb.parallels.com/131014/

Could the builds be automatically triggered, for example weekly if a script discovers new releases?

[Stromweld]

we have never automated the builds. I have it as a todo in the changelog in a small laundry list of things I'd like to do. Unfortunately I'm the only one actively maintaining it on my free time mostly.

[Stromweld]

Every 3-6 months I have to manually build all the vagrant boxes and publish them. GHA builds haven't been the most reliable. Some GHA builds are done on my home servers with self-hosted runners due to inability to automate parallels, vmware, installs etc... on GHA public runners.

[Stromweld]

I'm happy to review and merge pull requests for updated versions and or any other updates that help enhance the project. I try to keep up with updates on the runners but is a dance to update virtualzation providers, packer, and packer plugins without things breaking each other or my build servers.

[reneleonhardt]

Thank you for the peak behind the curtains 😄
I can imagine, it's very hard to find maintainers nowadays... thank you for your work!

Which parts and builds could contributions update or even automate here if not everything is possible on GHA public runners?

[Stromweld]

If there is anyway to automate install and initialization of parallels and vmware-(workstation/fusion) on GHA public runner. As well as some OS builds still need troubleshooting for failures. I have a table in the changelog.md of all the OS builds and which ones work and don't.