Skip to content

[SK-631] chore(deps): bump 5 low-risk Python deps#167

Merged
Avinash-Kamath merged 1 commit into
mainfrom
claude/vibrant-cray-w7v11x
Jun 11, 2026
Merged

[SK-631] chore(deps): bump 5 low-risk Python deps#167
Avinash-Kamath merged 1 commit into
mainfrom
claude/vibrant-cray-w7v11x

Conversation

@dhawani

@dhawani dhawani commented Jun 11, 2026

Copy link
Copy Markdown
Contributor

Summary

Relaxes/updates 5 low-risk dependency constraints in setup.py that were either blocking newer compatible versions or using overly tight pins.

Linear: https://linear.app/scalekit/issue/SK-631

Changes

Package From To Notes
setuptools >=78.1.1,<81.0 >=78.1.1,<83.0 Raise upper cap; 81.x and 82.x are stable
python-dotenv ~=1.1.1 >=1.1.1,<2.0 Relax tight pin; 1.2.x is backward-compatible
Faker ~=25.8.0 >=33.0.0,<41.0 Test-only dep; update to modern range (latest 40.23.0)
requests >=2.32.3 >=2.34.0 Bump lower bound to current stable
PyJWT >=2.12.0 >=2.13.0 Bump lower bound to current stable

Test Results

pip install -e . resolves cleanly with new constraints. pip check reports no broken requirements.

Notes

  • No source code changes required — all are constraint-only updates
  • Faker is used exclusively in tests (not in scalekit/ production code)
  • No behavioral or API changes in any of these packages affect the SDK

Generated by Claude Code

- setuptools: <81.0 → <83.0 (unblock 81.x/82.x)
- python-dotenv: ~=1.1.1 → >=1.1.1,<2.0 (allow 1.2.x)
- Faker: ~=25.8.0 → >=33.0.0,<41.0 (test-only dep, modern range)
- requests: >=2.32.3 → >=2.34.0 (bump lower bound)
- PyJWT: >=2.12.0 → >=2.13.0 (bump lower bound)

https://linear.app/scalekit/issue/SK-631
@dhawani dhawani requested a review from Avinash-Kamath as a code owner June 11, 2026 11:47
@coderabbitai

coderabbitai Bot commented Jun 11, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@dhawani, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 1 minute and 34 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 145c0959-b205-415c-834b-d95a8c26362b

📥 Commits

Reviewing files that changed from the base of the PR and between 246d4b9 and 41e5a59.

📒 Files selected for processing (1)
  • setup.py
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/vibrant-cray-w7v11x

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

@Avinash-Kamath Avinash-Kamath merged commit b01b7ee into main Jun 11, 2026
2 of 4 checks passed
@Avinash-Kamath Avinash-Kamath deleted the claude/vibrant-cray-w7v11x branch June 11, 2026 13:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants