Dont use constraints file in scheduled builds
diff --git a/.github/scripts/build_info.py b/.github/scripts/build_info.py
index 1853329b60c6..390a057ab1e4 100755
--- a/.github/scripts/build_info.py
+++ b/.github/scripts/build_info.py
@@ -89,6 +89,7 @@
 class GithubEvent(enum.Enum):
     PULL_REQUEST = "pull_request"
     PUSH = "push"
+    SCHEDULE = "schedule"
 
 
 def get_changed_files() -> List[str]:
@@ -182,6 +183,8 @@ def is_canary_build() -> bool:
     For push event, we return true when the default branch is checked. In other case,
     we return false.
 
+    For scheduled event, we always return true.
+
     For other events, we return false
     """
     if GITHUB_EVENT_NAME == GithubEvent.PULL_REQUEST.value:
@@ -208,8 +211,15 @@ def is_canary_build() -> bool:
             )
             return True
         return False
+    elif GITHUB_EVENT_NAME == GithubEvent.SCHEDULE.value:
+        print(
+            "Current build is canary, "
+            f"because current github event name is {GITHUB_EVENT_NAME!r}"
+        )
+        return True
+
     print(
-        "Current build is canary, "
+        "Current build is NOT canary, "
         f"because current github event name is {GITHUB_EVENT_NAME!r}"
     )
     return False
diff --git a/.github/workflows/python-versions.yml b/.github/workflows/python-versions.yml
index 5ee8c8458f24..7cea0fdaae5b 100644
--- a/.github/workflows/python-versions.yml
+++ b/.github/workflows/python-versions.yml
@@ -134,7 +134,11 @@ jobs:
       contents: write
 
     runs-on: ubuntu-latest
-    if: github.repository == 'streamlit/streamlit' && github.event_name == 'push' && github.ref_name == 'develop'
+    if: |
+      github.repository == 'streamlit/streamlit' && (
+      (github.event_name == 'push' && github.ref_name == 'develop') ||
+      (github.event_name == 'schedule')
+      )
 
     name: Upload constraints
 

<!--
Before contributing (PLEASE READ!)

⚠️ If your contribution is more than a few lines of code, then prior to starting to code on it please post in the issue saying you want to volunteer, then wait for a positive response. And if there is no issue for it yet, create it first.

This helps make sure:

  1. Two people aren't working on the same thing
  2. This is something Streamlit's maintainers believe should be implemented/fixed
  3. Any API, UI, or deeper architectural changes that need to be implemented have been fully thought through by Streamlit's maintainers
  4. Your time is well spent!

More information in our wiki: https://github.com/streamlit/streamlit/wiki/Contributing
-->

## 📚 Context
Currently, the constraints files are updated when a new PR is merged into the `develop` branch.
After merging, the constraints files will be updated by scheduled builds as well, so these files will be updated at least once a day.


_Please describe the project or issue background here_

- What kind of change does this PR introduce?

  - [ ] Bugfix
  - [ ] Feature
  - [ ] Refactoring
  - [ ] Other, please describe:

## 🧠 Description of Changes

- _Add bullet points summarizing your changes here_

  - [ ] This is a breaking API change
  - [ ] This is a visible (user-facing) change

**Revised:**

_Insert screenshot of your updated UI/code here_

**Current:**

_Insert screenshot of existing UI/code here_

## 🧪 Testing Done

- [ ] Screenshots included
- [ ] Added/Updated unit tests
- [ ] Added/Updated e2e tests

## 🌐 References

_Does this depend on other work, documents, or tickets?_

- **Issue**: Closes #XXXX

---

**Contribution License Agreement**

By submitting this pull request you agree that all contributions to this project are made under the Apache 2.0 license.
