v3 Azure Functions running old code after successful Bitbucket CI/CD deployment

We've got Bitbucket continuous deployment set up for a couple of our v3 Azure Functions (Azure Function App -> Platform Features -> Container settings -> CI/CD (Bitbucket)). No build provider selected, as the Bitbucket option doesn't seem to allow for it. Trigger branch is master. Function app is running from package. All are HTTP trigger functions. Nothing fancy.

Whenever we commit to master, it does indeed trigger a deployment-- which completes successfully. I can see the commit that triggered the deployment and all of that. The problem is, the function is still (usually) running old code after this deployment. I've tried restarting the function app, no success. I've tried completely stopping the app waiting for a bit and restarting, no success. Sometimes even manual deployment from Visual Studio doesn't work.

Once I remove the CI/CD pipe from Bitbucket, however, things go back to normal as far as manual deployments from VS go.

I've been able to reproduce this effect several times. Please let me know if you need any additional information.

Start by reproducing the deployment flow described for v3 Azure Functions: Bitbucket CI/CD on the master branch, running from package, followed by an HTTP-trigger request. Compare the deployed commit with the code served after deployment, restart, stop/start, and manual Visual Studio deployment. Done means the documented deployment path consistently serves the newly committed code.

Written by the indexing model from the issue text.