Your service deploys from a Docker image on the latest tag, and image auto updates are already turned on with a maintenance window that allows updates at any time. When we detect a new image pushed to that same tag, we redeploy the service to pull the new digest automatically.

Detection results are cached for up to a few hours to avoid overloading registries, so a fresh push from GitHub Actions can take a while to be picked up. Once an update is detected, an update button also appears in the service's Settings tab under the Source section, and you can use it to apply the new image right away. More detail is in the image auto updates docs.

turning off auto updates did not fix the issue either

The Restart option in that menu restarts the existing container without pulling a new image, so it will not pick up your latest push. To deploy the new image, open the service, press Cmd+K (Ctrl+K on Windows/Linux) to open the command palette, and select "Redeploy source image", which pulls the image again from the registry.