ROB-3755 - Update development dependencies to latest versions#2054
ROB-3755 - Update development dependencies to latest versions#2054naomi-robusta merged 2 commits intomasterfrom
Conversation
Bump tornado to ^6.5.5 (CVE-2026-31958 / GHSA-78cv-mqj4-43f7, CVE-2026-35536), black to 26.3.1 (CVE-2026-32274), and Pillow to ^12.2.0 (CVE-2026-40192) to address vulnerabilities in dev/docs dependencies.
|
✅ Docker image ready for
Use this tag to pull the image for testing. 📋 Copy commandsgcloud auth configure-docker us-central1-docker.pkg.dev
docker pull us-central1-docker.pkg.dev/robusta-development/temporary-builds/robusta-runner:54407aa
docker tag us-central1-docker.pkg.dev/robusta-development/temporary-builds/robusta-runner:54407aa me-west1-docker.pkg.dev/robusta-development/development/robusta-runner-dev:54407aa
docker push me-west1-docker.pkg.dev/robusta-development/development/robusta-runner-dev:54407aaPatch Helm values in one line: helm upgrade --install robusta robusta/robusta \
--reuse-values \
--set runner.image=me-west1-docker.pkg.dev/robusta-development/development/robusta-runner-dev:54407aa |
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
WalkthroughUpdated dev dependency versions in Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
naomi-robusta
changed the title
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
pyproject.toml (1)
10-12:⚠️ Potential issue | 🟡 MinorUpdate black target-version to match project Python version.
The black configuration specifies
target-version = ['py37']but the project requires Python>=3.10, <3.12(line 20). This mismatch means black may not utilize Python 3.10+ syntax features or could apply incorrect formatting rules.🔧 Proposed fix to align target-version with project Python version
[tool.black] line-length = 120 -target-version = ['py37'] +target-version = ['py310', 'py311']🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@pyproject.toml` around lines 10 - 12, The Black config under [tool.black] currently sets target-version = ['py37'], which mismatches the project's Python requirement (>=3.10,<3.12); update the target-version setting to match supported interpreters (e.g., target-version = ['py310', 'py311'] or at minimum ['py310']) so Black will use Python 3.10+ formatting rules; modify the target-version key in the [tool.black] section accordingly.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@pyproject.toml`:
- Line 108: The dependency line setting Black to "26.3.1" may change formatting
results compared to 22.3.0; run the formatter across the repo with Black 26.3.1
(using the pyproject.toml setting "black = \"26.3.1\"") and review/commit any
formatting diffs, and re-enable or add the Black pre-commit hook in
.pre-commit-config.yaml so CI enforces the new formatter; if formatting changes
are unacceptable, adjust configuration (pyproject.toml Black options) or pin to
a different Black-compatible version and update tests/CI accordingly.
---
Outside diff comments:
In `@pyproject.toml`:
- Around line 10-12: The Black config under [tool.black] currently sets
target-version = ['py37'], which mismatches the project's Python requirement
(>=3.10,<3.12); update the target-version setting to match supported
interpreters (e.g., target-version = ['py310', 'py311'] or at minimum ['py310'])
so Black will use Python 3.10+ formatting rules; modify the target-version key
in the [tool.black] section accordingly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 38eb5f9b-b9af-47b3-bc1c-ac23322662ec
⛔ Files ignored due to path filters (1)
poetry.lockis excluded by!**/*.lock
📒 Files selected for processing (1)
pyproject.toml
The previous commit was locked with poetry 2.3.3 (lock-version 2.1), which fails the pre-commit poetry-lock hook pinned to poetry 1.8.5. Re-generate the lockfile in the 2.0 format expected by the hook.
3 participants
Summary
This PR updates several development dependencies to their latest versions to ensure compatibility, security, and access to new features.
Key Changes
^12.1.1to^12.2.022.3.0to26.3.1(major version bump)^6.5.1to^6.5.5Notes
These are development and documentation dependencies that support the build, testing, and code formatting workflows. The black formatter update is a significant version bump that may introduce changes to code formatting behavior.
https://claude.ai/code/session_01Y29n73kfj8vU7nRPHXk4Dk