fix: activation based on backend status

[HarshMN2345]

What does this PR do?

(Provide a description of what this PR does.)

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

Summary by CodeRabbit

• Bug Fixes
  • Improved deployment status evaluation to correctly determine when deployment actions should be available and enabled. This ensures the Activate button, Download submenu visibility, and output file downloads respond appropriately to all deployment state changes, including better handling of intermediate deployment states and finalization scenarios where status transitions were previously unclear.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[appwrite]

Console (appwrite/console)

Project ID: 688b7bf400350cbd60e9

Sites (1)

Site	Status	Logs	Preview	QR
console-stage 688b7cf6003b1842c9dc	Ready	View Logs	Preview URL

Tip

Environment variables can be scoped per function or shared across your project

[coderabbitai]

Walkthrough

This change modifies the deployment action menu component to introduce a refined status value for determining action availability. The update creates an actualStatus variable from deployment.status and derives a statusForActions variable that overrides the effective status with the actual status when the effective status is 'finalizing'. This derived status replaces the effective status in conditional checks across three areas: the readiness check for the Activate button, the visibility of the Download submenu, and the disabled state of the Download output anchor.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly matches the main change: fixing deployment activation logic to use backend status instead of derived status.
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.}

---

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