chore: Clean up event workers package

[adityachoudhari26]

Summary by CodeRabbit

• Chores
  • Removed unused dependencies for Redis interactions and semaphore management.
• Refactor
  • Streamlined the shutdown process by eliminating the Redis cleanup step.
  • Updated worker configurations by adjusting import references.
  • Discontinued background processing for release evaluation and associated mutex management.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request removes Redis-related dependencies and code from the project. In the package.json file, the dependencies for ioredis and redis-semaphore have been removed. The Redis connection code in src/redis.ts was deleted, and the shutdown process in src/index.ts was simplified to exclude any Redis cleanup steps. Additionally, an import path for a worker module was updated in src/workers/index.ts, and two files related to release evaluation—one implementing the evaluation worker and another handling mutex locking—were removed.

Changes

File(s)	Change Summary
apps/event-worker/package.json, apps/event-worker/src/index.ts, apps/event-worker/src/redis.ts	Removed Redis-specific dependencies, connection code, and the redis.quit() call from the shutdown sequence.
apps/event-worker/src/workers/index.ts	Updated the import path for newDeploymentVersionWorker from ./releases/new-deployment-version.js to ./new-deployment-version.js.
apps/event-worker/src/workers/releases/evaluate/index.ts, apps/event-worker/src/workers/releases/mutex.ts	Removed the release evaluation worker function and its associated mutex class used for managing Redis-based locks.

Sequence Diagram(s)

sequenceDiagram
    participant EW as Event Worker
    participant W as Workers
    participant P as Process
    EW->>W: Initiate graceful shutdown
    W-->>EW: Workers closed
    EW->>P: process.exit(0)

Loading

Possibly related PRs

• chore: Move workers to dir #445: Focused on removing Redis-related dependencies and updating module imports related to Redis functionality.
• feat: Deployment worker #446: Addressed similar changes in the worker import paths, notably affecting the newDeploymentVersionWorker reference.
• feat: Init new worker format #444: Involved modifications in worker management, including the removal of Redis cleanup logic within worker shutdown processes.

Poem

I hop through lines of code so light,
Saying goodbye to Redis tonight.
Dependencies shed like leaves in fall,
Smooth worker paths now enchant us all.
With whiskered cheer and a bounding leap,
My rabbit heart in refactored code shall keep!
🐇✨

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 31c12cb and fdc005c.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (6)

• apps/event-worker/package.json (0 hunks)
• apps/event-worker/src/index.ts (1 hunks)
• apps/event-worker/src/redis.ts (0 hunks)
• apps/event-worker/src/workers/index.ts (1 hunks)
• apps/event-worker/src/workers/releases/evaluate/index.ts (0 hunks)
• apps/event-worker/src/workers/releases/mutex.ts (0 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.

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.