Hi, @TomHall2020. Part of the issue here is a false assumption that you can reuse the same string for --alias deploys. You cannot. I have a post here which explains in more detail:
When you used --alias dev you locked dev to that exact deploy. That was deploy id 60ddf41693dc470008c3dd3a which was created on 2021-07-01 at 09:57:58 (UTC-07:00).
Your continued use of --alias dev will not cause the alias to update. You locked that to deploy id 60ddf41693dc470008c3dd3a on July 1st and it can never be changed again.
The other two deploys you linked to (60df696c37f112457c18ff85 and 60e1cb1ad44d371e8af57ad5) are not connected to dev--elastic-babbage-dd5d05.netlify.app in any way. Your changes in new deploys will never be reflected on the dev--elastic-babbage-dd5d05 subdomain because it is forever locked to 60ddf41693dc470008c3dd3a.
In other words, you cannot use the --alias option to simulate branch deploys. The are different deploy types (alias and branch deploys) and they do not work in the same way.
We do have an open feature request for the --alias deploys to create “real” branch deploys. If that feature becomes available, we will post an update here to let you know.
If there are other questions or concerns, please reply here anytime.