chore(deps): update dependency flask to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
flask (changelog)	==2.3.3 -> ==3.0.0
flask (changelog)	==2.2.5 -> ==3.0.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[richardli1598]

Hello, I am a code review bot on flows.network. Here are my reviews of changed source code files in this PR.

---

1. There is a discrepancy in the version of Flask updated across the different requirements.txt files. In some cases, the version was changed from 2.2.5 to 3.0.0, while in the requirements.txt at the end, it was updated from 2.3.3. This inconsistency could indicate that there might be an oversight in maintaining version parity across different environments or modules. Consistency is crucial for predictability and maintainability of the codebase. Version alignment should be verified to ensure that there is no specific reason for a different version being used in the general requirements.txt.

2. The patch updates Flask to a major version (3.0.0), which could introduce breaking changes or deprecations. There should be a thorough review within the application code to ensure compatibility with the new Flask version, and this should include running tests to confirm that the application functions as expected with the upgraded Flask version. Since major version upgrades can contain significant changes, it’s essential to understand the impact on the current code base.

3. There is also a small formatting issue in the tiktok-dlp/requirements.txt where it's mentioned "\ No newline at end of file". This is more of a stylistic issue, as POSIX standards suggest that a file should end with a newline. While not typically a problem, some tools might produce warnings or behave unexpectedly when processing files not ending with a newline.

4. It would be important to check the changelog or migration guide for Flask v3.0.0 to understand any changes that must be made in the code or configurations due to the new version. This would also include updating any Flask extensions that might not be compatible with Flask v3.0.0.

5. Finally, it is not indicated whether the other dependencies listed in the requirements.txt files are compatible with Flask v3.0.0. Dependency compatibility must be checked to prevent any issues from arising due to incompatibility between the Flask major version and other packages.

[netlify]

✅ Deploy Preview for kubespider ready!

Name	Link
🔨 Latest commit	e4ac695
🔍 Latest deploy log	https://app.netlify.com/sites/kubespider/deploys/65815f45cae4010008508296
😎 Deploy Preview	https://deploy-preview-422--kubespider.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.