Build(deps): Bump python from 3.11-slim to 3.14-slim

[dependabot]

Bumps python from 3.11-slim to 3.14-slim.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by CodeRabbit

• Chores
  • Updated the runtime environment to a newer version, improving security and compatibility with modern dependencies.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

The Dockerfile's base image has been updated from python:3.11-slim to python:3.14-slim. All other Dockerfile instructions remain unchanged.

Changes

Cohort / File(s)	Summary
Docker Configuration Dockerfile	Base image upgraded from python:3.11-slim to python:3.14-slim

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A hop, skip, and jump through the clouds so blue,
Python climbs higher—3.14 it's true!
From 3.11 we bid our fond farewell,
The Dockerfile dances, with tales it will tell! 🎪

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: updating the Python base Docker image from version 3.11-slim to 3.14-slim, which accurately reflects the single-line modification in the Dockerfile.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 10f22ec and 7bd890a.

📒 Files selected for processing (1)

• Dockerfile

🔇 Additional comments (1)

Dockerfile (1)

2-2: Python 3.14 is stable and available. The python:3.14-slim Docker image exists on Docker Hub and is actively maintained. No action needed.

The Docker image was released and last updated on January 2, 2026. Python 3.14 stable was released on October 7, 2025, well before this change date. All dependencies in requirements.txt (Celery, Pillow, Pydantic, SQLAlchemy, Psycopg2, Streamlit, Pandas, etc.) are recent versions with confirmed Python 3.14 support.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Shashank0701-byte]

Good catch bot, but skipping for now to maintain stability

[Shashank0701-byte]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[Shashank0701-byte]

@coderabbitai shall i go ahead with the merge ?

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check the Dockerfile to understand the application
cat Dockerfile

# Check for test files in the repository
fd -e py test

# Check for CI/CD configuration files
fd -e yml -e yaml .github

# Check if there's a requirements.txt or pyproject.toml
fd requirements.txt
fd pyproject.toml

# Check for any Python version specifications in other files
rg "python.*3\.(11|12|13|14)" -g '!.git'

Length of output: 901

---

🌐 Web query:

Python 3.14 release date status

💡 Result:

Python 3.14 was released (final) on October 7, 2025. [1][2]

Sources:

• PEP 745 (3.14 release schedule). [1]
• Python.org release / Python Insider blog announcing 3.14.0 final. [2]

---

🏁 Script executed:

#!/bin/bash
# Check PR status and CI checks using GitHub CLI
gh pr view 13 --json statusCheckRollup,reviews,mergeable

# Check requirements.txt for any Python version constraints
cat requirements.txt

# Check if there's any GitHub Actions workflow
fd . .github/workflows

# Look for any version-specific code or deprecation warnings
rg -n "sys.version_info|version_info|DeprecationWarning" --type py

Length of output: 857

---

🏁 Script executed:

#!/bin/bash
# Look for GitHub Actions workflows in the repo
fd -t f . .github/ 2>/dev/null

# Check if there are any test results or pytest configurations
fd pytest.ini
fd setup.py
fd pyproject.toml

# Check the actual test files to understand test coverage
cat tests/test_parser.py

# Look for any Python version compatibility issues in the dependencies
cat requirements.txt | head -20

Length of output: 2047

---

@Shashank0701-byte, I noticed you previously mentioned "skipping for now to maintain stability" in your approval, so I want to provide you with a complete picture before you decide:

⚠️ Important Considerations

Python 3.14 Status:
Python 3.14 was released on October 7, 2025, making it only ~3 months old. This is a relatively new release that may have:

• Compatibility issues with some dependencies
• Undiscovered bugs in the runtime
• Limited production battle-testing

This is a significant jump: Going from Python 3.11 → 3.14 (skipping 3.12 and 3.13) increases the risk of encountering breaking changes.

✅ What Looks Good

• Your dependencies appear modern and should generally support Python 3.14
• The PR is mergeable with no conflicts
• CodeRabbit checks passed

🧪 Recommended Testing Before Merge

Since I don't see automated CI/CD test results, I recommend:

1. Test locally first:

   docker build -t docuflow-test .
   docker run docuflow-test pytest tests/

2. Verify key functionality:

   • OCR processing (pytesseract)
   • PDF parsing (pdf2image, poppler)
   • Database connections (psycopg2-binary)
   • Celery task queue
   • Streamlit dashboard

💡 Alternative Approach

Consider a gradual upgrade path for better stability:

• First upgrade to Python 3.12 or 3.13 (more mature releases)
• Test thoroughly in production
• Then upgrade to 3.14 later when it's more battle-tested

My recommendation: If stability is your priority (as your earlier comment suggests), I'd wait or test extensively before merging. If you want to be on the cutting edge and can afford some risk, go ahead but monitor closely in production.

What's your priority - stability or having the latest version?