No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

(To be clear, there are no official caches listed on my github actions management page)

Alright--here’s the workaround I worked up, for anyone interested.

1. Create an actual lock on the stack by starting a `pulumi refresh`
2. Copy/paste/rename it to match the phantom lock
3. Complete the refresh
4. Finally `gsutil rm <gs://mybucket/.pulumi/locks/test/33cd4732-e6ea-4e4f-a901-12777979d41a.json>` to delete the fake lock (NB the URL is slightly different)
Voila! The :ghost: is gone!