Acmebot v5 - Early Preview Release

[shibayan]

We’re excited to announce the initial release of Acmebot v5!
This version introduces a major migration to .NET Isolated, enabling deployment to Azure Functions Flex Consumption for the first time.

Please note that as part of this transition, some potential issues may still exist during the early preview phase.
Our goal is to deliver the official stable release alongside the GA of .NET 10.

Migrate steps

1. Set FUNCTIONS_WORKER_RUNTIME = dotnet-isolated
2. Remove FUNCTIONS_INPROC_NET8_ENABLED
3. Set WEBSITE_RUN_FROM_PACKAGE = https://stacmebotprod.blob.core.windows.net/acmebot/v5/latest.zip

Update (2026/02/20):

We’ve added deployment templates to easily deploy Acmebot v5 on Azure Functions Flex Consumption.
You can now get started quickly by deploying directly from the README.

At the same time, the dashboard has been redesigned and polished with a brand-new, more refined UI.

[shibayan]

Alongside the release of Acmebot v5, we plan to change the repository name from keyvault-acmebot to Acmebot.

[jagiraud]

I suppose there are more changes needed?
Flex consumption environment settings in does not allow ":" in the name, for example Acmebot:Endpoint, I'm guessing these should be changed to: Acmebot__Endpoint?

[shibayan]

Yes, that understanding is correct. In Flex Consumption, you need to replace : with __.

[mvanlaar]

Can you update the wiki also for this?

[shibayan]

The Wiki has been updated to the latest version.

[NotZircom]

The website indicates that v5 is preferred for new production deployments, but the readme still says its only in preview and production deployments should use v4. Which is the case?

[endgor]

What is the correct way to upgrade from one v5 RC to another? The deployment script requires many parameters to be set. Should I specify the same names as those we have already deployed and then run the script?