Upgrade dependencies

[brylie]

This pull request updates the pyproject.toml file to adjust dependencies for the project. The changes primarily involve moving django-tailwind[reload] from the main dependencies list to the development dependencies list.

Dependency adjustments:

• pyproject.toml: Removed django-tailwind[reload]>=4.0.1 from the main dependencies list.
• pyproject.toml: Added django-tailwind[reload]>=4.0.1 to the dev dependencies list.

Summary by Sourcery

Reorganize dependency management by moving development-only packages out of production and tidying up the requirements files.

Enhancements:

• Clean up production requirements by removing development-specific packages such as django-tailwind, django-browser-reload, django-crispy-forms, and crispy-bootstrap5.

Chores:

• Move django-tailwind[reload] from the main dependencies to the dev dependencies in pyproject.toml.

Summary by CodeRabbit

• Chores
  • Updated project dependencies by removing several packages related to form handling and styling.
  • Adjusted development dependencies for improved environment management.

[sourcery-ai]

Reviewer's Guide

Reorganizes project dependencies by migrating django-tailwind[reload] from the main to development section in pyproject.toml, pruning related entries in requirements.txt, and regenerating the lock file to reflect these updates.

File-Level Changes

Change	Details	Files
Reassign django-tailwind[reload] to dev dependencies	Removed django-tailwind[reload]>=4.0.1 from the main dependencies list Added django-tailwind[reload]>=4.0.1 under the dev dependencies section	pyproject.toml
Prune redundant dependency entries in requirements.txt	Removed crispy-bootstrap5, django-crispy-forms, and django-browser-reload entries Cleaned up outdated comments and hash blocks Adjusted via annotations for Django-related packages	requirements.txt
Regenerate lock file to sync updated dependencies	Refreshed uv.lock after dependency modifications	uv.lock

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Walkthrough

The dependency management files were updated to remove the packages "crispy-bootstrap5", "django-crispy-forms", and "django-tailwind" from the main requirements. "django-tailwind" was moved to the development dependencies section. Associated comments and hash entries were also cleaned up, with no changes to other dependencies or public entity declarations. Additionally, the Django settings were updated to remove the apps "crispy_bootstrap5" and "crispy_forms" from the installed apps list.

Changes

File(s)	Change Summary
pyproject.toml	Removed "crispy-bootstrap5", "django-crispy-forms", and "django-tailwind[reload]>=4.0.1" from main deps; moved "django-tailwind[reload]>=4.0.1" to dev dependencies.
requirements.txt	Removed "crispy-bootstrap5", "django-browser-reload", "django-crispy-forms", and "django-tailwind" with associated hashes and comments. Simplified one dependency comment.
core/settings.py	Removed "crispy_bootstrap5" and "crispy_forms" from INSTALLED_APPS.

Poem

🐇
Spring cleaning in the garden of code,
Old dependencies packed and stowed.
Tailwind hops to dev’s new den,
Crispy forms say bye again.
With lighter packs, we bound along—
The project’s path is clear and strong!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b323848 and b5411bb.

📒 Files selected for processing (1)

• core/settings.py (0 hunks)

💤 Files with no reviewable changes (1)

• core/settings.py

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: runner-job
• GitHub Check: Analyze (actions)
• GitHub Check: Analyze (javascript)
• GitHub Check: Analyze (python)

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sourcery-ai]

Hey @brylie - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.60%. Comparing base (0e43c53) to head (b5411bb).
Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1160   +/-   ##
=======================================
  Coverage   94.60%   94.60%           
=======================================
  Files         110      110           
  Lines        2966     2966           
=======================================
  Hits         2806     2806           
  Misses        160      160           

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