fix: Trigger releaseId -> versionId refactor

[adityachoudhari26]

Summary by CodeRabbit

• Refactor
  • Standardized the platform’s identifier approach to ensure that job, deployment, and resource links consistently use version-based identifiers.
• Bug Fixes
  • Improved data consistency and navigation accuracy across job tracking and deployment status displays for a more reliable user experience.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This PR consistently replaces the use of the releaseId field with versionId throughout the codebase. Changes affect SQL join conditions, query filters, URL constructions, and test objects across apps, API routes, job dispatch modules, policies, and even the database schema. The modification shifts the relational logic between the releaseJobTrigger and deploymentVersion tables, with no changes to the exported or public entities aside from the schema field rename. Overall, this update realigns the identifier naming convention to use versionId instead of releaseId.

Changes

File(s)	Change Summary
apps/event-worker/src/job-dispatch/github.ts, apps/jobs/src/policy-checker/index.ts, apps/timeout-checker/index.ts, apps/webservice/src/app/.../ReleaseCell.tsx, apps/webservice/src/app/api/v1/...	Updated join conditions and URL references by replacing releaseId with versionId in queries and link construction.
packages/api/src/router/...	Modified SQL join conditions across various API routes (e.g., deployment, environment, job, resource stats) to use versionId instead of releaseId.
packages/job-dispatch/src/... (including tests and policies)	Refactored join conditions, filtering criteria, and object properties in job dispatch modules and policies, transitioning from releaseId to versionId.
packages/auth/src/utils/rbac.ts, packages/db/src/schema/release.ts	Updated join logic in authentication utilities and renamed the releaseId field to versionId in the releaseJobTrigger table schema.

Possibly related PRs

• fix: Optimize job policy query #153 – Both PRs modify join conditions in the releaseJobTrigger queries to transition from releaseId to versionId.
• fix: Optimize flow node query #190 – Directly related changes that also update join conditions to use versionId, aligning job trigger processing with new identifier logic.
• fix: Minimum release interval policy #272 – Involves similar modifications in join criteria and introduces new policies, showing a consistent shift toward using versionId across the codebase.

Poem

I'm a bunny hopping through the code,
Swapping releaseId for versionId down the road.
SQL joins now sing a different tune,
With cleaner paths under the same moon.
Carrots in hand, the changes are a delight—
Hopping to new beats, keeping code just right!
🥕🐇

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

📜 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 9c5d3e7 and 7db642f.

📒 Files selected for processing (2)

• packages/db/drizzle/meta/0076_snapshot.json (65 hunks)
• packages/db/drizzle/meta/_journal.json (1 hunks)

---

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