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

```$ pulumi about                                                                                                                                                                                                                                        
CLI
Version      3.46.1
Go Version   go1.19.2
Go Compiler  gc

Plugins
NAME        VERSION
aws         5.21.0
aws-native  0.41.0
awsx        1.0.0-beta.11
docker      3.6.0
python      unknown

Host
OS       darwin
Version  13.0
Arch     x86_64```

oh… I guess it’s in state, fixed:
```pulumi state delete urn:pulumi:uat::env-app::pulumi:providers:aws-native::default```

My theory is that old resources that don't get redeployed continue to refer to the older plugins, at least in the state file. Once every resource (that was deployed with version X) is updated using any newer version of the plugin, then Pulumi will drop the reference to version X.
This is based only on my own non-empirical observations of state files.

I just ran into this again, this time with a newer version of the plugin that has gone missing, `aws-native-0.41.1-alpha.1669144866`

With CICD, this will cause intermittent failures.

Is it a good idea to start CICD runs by first removing the provider every run?

There should be now (since 1h) a 0.42.0 version

I check with engineering, why this happens