chore: Update requirements.txt

[ruuushhh]

Description

chore: Update requirements.txt

Clickup

https://app.clickup.com/

Summary by CodeRabbit

• Chores
  • Updated framework dependency to the latest patch version for improved stability and security.

[coderabbitai]

Walkthrough

The pull request updates the Django dependency in requirements.txt from version 4.2.27 to 4.2.28, a patch-level version bump. No other dependencies or project files are modified.

Changes

Cohort / File(s)	Summary
Dependency Update requirements.txt	Django patched from 4.2.27 to 4.2.28

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: upgrade django to 4.2.27 #158: Bumps Django patch version in requirements.txt from 4.2.26 to 4.2.27, showing a pattern of incremental Django patch updates.

Suggested labels

size/XS

Suggested reviewers

• ashwin1111
• Ashutosh619-sudo

Poem

🐰 A hop, a skip, a patch so small,
Django 4.2.28 answers the call,
Bugs fixed, security tight,
Requirements refresh, everything right! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: a dependency update in requirements.txt (Django 4.2.27 → 4.2.28).
Description check	✅ Passed	The description follows the required template structure with Description and Clickup sections, though the description content is minimal and generic.
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.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch upgrade-django-4.2.28

---

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.}

[github-actions]

Coverage Report

File	Stmts	Miss	Cover	Missing
apps/fyle
actions.py	15	0	100%
exceptions.py	41	25	39%	20–53
helpers.py	50	6	88%	22–23, 34, 153–155
models.py	64	0	100%
queue.py	22	1	95%	74
tasks.py	91	8	91%	71–76, 133–138
views.py	19	2	89%	36–38
apps/mappings
actions.py	5	0	100%
connector.py	69	0	100%
models.py	18	0	100%
serializers.py	12	0	100%
views.py	23	0	100%
apps/qbd
helpers.py	57	0	100%
models.py	283	6	98%	22, 28, 39–45, 172
queue.py	11	0	100%
tasks.py	123	0	100%
apps/tasks
models.py	19	0	100%
serializers.py	6	0	100%
views.py	37	0	100%
apps/users
models.py	14	0	100%
views.py	16	0	100%
apps/utils/email
email.py	20	0	100%
apps/utils/iif_generator
iif_generator.py	30	0	100%
schemas.py	1	0	100%
apps/workspaces
models.py	89	0	100%
permissions.py	20	1	95%	22
schedule.py	46	0	100%
serializers.py	104	10	90%	29, 159–161, 178–179, 226–229
tasks.py	98	13	87%	41–42, 150–151, 190–206
views.py	53	0	100%
tests
conftest.py	97	4	96%	280–284
tests/test_fyle
fixtures.py	1	0	100%
test_helpers.py	11	0	100%
test_queue.py	20	0	100%
test_tasks.py	103	2	98%	299–300
test_view.py	53	0	100%
tests/test_mapping
fixtures.py	1	0	100%
test_connector.py	57	0	100%
test_view.py	47	0	100%
tests/test_qbd
conftest.py	10	0	100%
test_queue.py	29	0	100%
test_tasks.py	308	0	100%
tests/test_tasks
test_views.py	44	0	100%
tests/test_users
test_views.py	9	0	100%
tests/test_utils
fixtures.py	1	0	100%
test_iif_generator.py	39	0	100%
tests/test_workspaces
test_schedules.py	44	0	100%
test_tasks.py	97	2	98%	270–271
test_views.py	148	0	100%
TOTAL	2575	80	97%

Tests	Skipped	Failures	Errors	Time
68	0 💤	0 ❌	0 🔥	9.860s ⏱️

[github-actions]

---

Diff Coverage
Diff: origin/master..HEAD, staged and unstaged changes

No lines with coverage information in this diff.