Skip to content

[ENG-318] Bump Packages, Linting#3645

Merged
vigneshhari merged 1 commit into
developfrom
ENG-318-routine-package-upgrades
May 15, 2026
Merged

[ENG-318] Bump Packages, Linting#3645
vigneshhari merged 1 commit into
developfrom
ENG-318-routine-package-upgrades

Conversation

@vigneshhari
Copy link
Copy Markdown
Member

@vigneshhari vigneshhari commented May 15, 2026

Bump Packages, Linting : ENG-318

Summary by CodeRabbit

  • Chores

    • Updated multiple package dependencies to latest versions for enhanced security and performance.
  • Updates

    • Modified questionnaire field naming in API responses to use standardized conventions.

Review Change Stack

@vigneshhari vigneshhari requested a review from a team as a code owner May 15, 2026 05:29
Copy link
Copy Markdown

@greptile-apps greptile-apps Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 15, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 2ef76126-838b-4181-b8be-5a09c626c193

📥 Commits

Reviewing files that changed from the base of the PR and between a7fd21c and 7bac6de.

⛔ Files ignored due to path filters (1)
  • Pipfile.lock is excluded by !**/*.lock
📒 Files selected for processing (2)
  • Pipfile
  • care/emr/resources/questionnaire/spec.py

📝 Walkthrough

Walkthrough

This PR updates dependency versions across the application and simplifies the Question schema by removing a Pydantic field alias. The dependency changes span main packages (authlib, boto3, pillow, psycopg, requests, pydantic) and dev tooling (mypy, werkzeug, ruff); the schema change eliminates camelCase alias mapping from answer_constraint.

Changes

Dependency and Schema Updates

Layer / File(s) Summary
Dependency version updates
Pipfile
Main packages (authlib, boto3, pillow, psycopg, requests, pydantic, urllib3, etc.) and dev packages (boto3-stubs, mypy, werkzeug, ruff, pre-commit) are bumped to newer pinned or minor versions.
Questionnaire schema field simplification
care/emr/resources/questionnaire/spec.py
The Question.answer_constraint field drops its Pydantic Field(alias="answerConstraint", default=None) wrapper and becomes a direct annotation: answer_constraint: AnswerConstraint | None = None.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description is severely incomplete, missing nearly all required template sections including Proposed Changes details, Associated Issue link, and Merge Checklist. Expand description to include all template sections: detailed Proposed Changes, issue link, and complete Merge Checklist with checkmarks for completed items.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title 'ENG-318 Bump Packages, Linting' clearly describes the main changes: dependency updates and linting improvements.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ENG-318-routine-package-upgrades

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


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

@codecov
Copy link
Copy Markdown

codecov Bot commented May 15, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.45%. Comparing base (6a0b7d7) to head (7bac6de).
⚠️ Report is 5 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #3645      +/-   ##
===========================================
- Coverage    75.54%   75.45%   -0.10%     
===========================================
  Files          478      479       +1     
  Lines        22931    22986      +55     
  Branches      2369     2375       +6     
===========================================
+ Hits         17323    17343      +20     
- Misses        5038     5070      +32     
- Partials       570      573       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@vigneshhari vigneshhari merged commit 205669f into develop May 15, 2026
11 of 13 checks passed
@vigneshhari vigneshhari deleted the ENG-318-routine-package-upgrades branch May 15, 2026 10:58
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.

1 participant