Streamlit versions mismatch

Deployment
1

Hi,

I built an app with streamlit version 1.32.0 on my local and deployed it on streamlit server. I have a requirements.txt which calls for streamlit==1.32.0. But when I refresh the deployed app, looks like streamlit version is upgraded to latest one and as a result of this, some of the functions are throwing errors as the options/syntax has changed.

Is there any workaround for this?

any help is greatly appreciated.

Thank you

image
image637×325 75 KB

2

Hey there, thanks for reaching out and sharing your experience (and the screenshot)! :tada: This is a common pain point, and you’re not alone. When you specify streamlit==1.32.0 in your requirements.txt, Streamlit Community Cloud should respect that version and not auto-upgrade. However, there have been recent reports and forum discussions about the platform sometimes upgrading Streamlit despite a pinned version, especially after a reboot or refresh, due to internal dependency resolution quirks or platform-side pinning overrides.

Workaround:

  • Double-check that your requirements.txt is in the root of your repo and contains only one line for Streamlit, e.g., streamlit==1.32.0.
  • If the issue persists, try deleting and redeploying your app, as this sometimes resets the environment and respects the pinned version (see this discussion).
  • If you still see auto-upgrades, it may be due to a temporary platform-side pin or bug. In that case, keep an eye on Streamlit Community Cloud status and related forum threads.

For best reliability, always pin all critical dependencies in requirements.txt and redeploy if you notice version drift. If you’re still stuck, please share your repo or a minimum reproducible example so the community can help debug further!

Sources: