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

fixed the issue.
had in the requirement: `pulumi-docker&gt;=3.4.1&lt;4.0.0`
which pulled in `pulumi-docker-3.5.0a1660680787` which is an alpha version i assume.
fixed the issue by pinning the version to `==3.6.1`
and then had to delete the provider reference in the state.
would it be possible to release alpha pip packages such that they are not installed when providing a range version in pip `requirements.txt`?

I thought that was already standard pip behaviour?

See <https://pip.pypa.io/en/stable/cli/pip_install/#cmdoption-pre>

may be because there is a dot missing ?
`pulumi-docker-3.5.0a1660680787` -&gt; pulumi-`docker-3.5.0.a1660680787`

Also brew does look to have 3.51 available: <https://github.com/Homebrew/homebrew-core/blob/master/Formula/pulumi.rb>

That's a pretty old version of pip. Can you upgrade it and try again?
May as well recreate your venv as well

```python -m pip install 'pulumi-docker&gt;=3.4.1,&lt;4.0.0'
Collecting pulumi-docker&lt;4.0.0,&gt;=3.4.1
  Downloading pulumi_docker-3.6.1.tar.gz (86 kB)```


<@U02J3T6A8LB> that's some amazing Eagle eyes you have there :joy:

interesting. this missing comma makes pip pull alpha versions.

may be a  check for pulumi plugins may be good. to ensure no alphas are used without an explicit opt-in.