[#1695] Renamed deps updates.

[AlexSkrypnyk]

closes #1695

Summary by CodeRabbit

• Chores

  • Updated naming conventions for dependency update workflows and jobs to use "update-dependencies" instead of "deps-updates" across configuration files and workflows for improved consistency.

• Tests

  • Updated test cases to reflect the new workflow and job names for dependency updates.

[coderabbitai]

Walkthrough

The changes standardize naming conventions for dependency update workflows and jobs by renaming all references from deps-updates to update-dependencies across CircleCI, GitHub Actions, code logic, and tests. No functional logic or workflow steps were altered—only identifiers and filenames were updated for consistency.

Changes

File(s)	Change Summary
.circleci/config.yml, .github/workflows/update-dependencies.yml	Renamed job, workflow, and parameter identifiers from deps-updates to update-dependencies.
.vortex/installer/src/Prompts/Handlers/DependencyUpdatesProvider.php	Updated internal logic to reference update-dependencies.yml and update-dependencies strings.
.vortex/installer/tests/Unit/PromptManagerTest.php	Updated test setup to use new workflow filename and job identifier in simulated project directories.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CI System (CircleCI/GitHub Actions)
    participant DependencyUpdatesProvider

    User->>CI System (CircleCI/GitHub Actions): Triggers "Update dependencies" workflow/job
    CI System (CircleCI/GitHub Actions)->>DependencyUpdatesProvider: Checks for "update-dependencies.yml"
    DependencyUpdatesProvider-->>CI System (CircleCI/GitHub Actions): Processes workflow/job as per new naming

Loading

Assessment against linked issues

Objective (Issue #)	Addressed	Explanation
Rename deps-updates.yml to update-dependencies.yml (#1695)	✅

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes found.

Possibly related PRs

• Added a manual trigger for Renovate in CircleCI. #1700: Introduced the original run_deps_updates parameter and deps-updates-manual workflow, which are directly renamed in this PR.

Poem

A rabbit hopped through fields of code,
Renaming files as it strode.
"Deps-updates" now takes its leave,
"Update-dependencies" we achieve!
With tidy names and tests in tow,
The garden of workflows continues to grow.
🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 0ba671a and d8126a3.

⛔ Files ignored due to path filters (9)

• .vortex/installer/tests/Fixtures/install/_baseline/.github/workflows/update-dependencies.yml is excluded by !.vortex/installer/tests/Fixtures/**
• .vortex/installer/tests/Fixtures/install/ciprovider_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
• .vortex/installer/tests/Fixtures/install/code_provider_other/.github/workflows/-update-dependencies.yml is excluded by !.vortex/installer/tests/Fixtures/**
• .vortex/installer/tests/Fixtures/install/deploy_type_all_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
• .vortex/installer/tests/Fixtures/install/deploy_type_none_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
• .vortex/installer/tests/Fixtures/install/deps_updates_provider_app/.github/workflows/-update-dependencies.yml is excluded by !.vortex/installer/tests/Fixtures/**
• .vortex/installer/tests/Fixtures/install/deps_updates_provider_ci_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
• .vortex/installer/tests/Fixtures/version_replacement/baseline/update-dependencies.yml is excluded by !.vortex/installer/tests/Fixtures/**
• .vortex/installer/tests/Fixtures/version_replacement/expected/update-dependencies.yml is excluded by !.vortex/installer/tests/Fixtures/**

📒 Files selected for processing (4)

• .circleci/config.yml (4 hunks)
• .github/workflows/update-dependencies.yml (2 hunks)
• .vortex/installer/src/Prompts/Handlers/DependencyUpdatesProvider.php (2 hunks)
• .vortex/installer/tests/Unit/PromptManagerTest.php (4 hunks)

🧰 Additional context used

🧬 Code Graph Analysis (1)

.vortex/installer/src/Prompts/Handlers/DependencyUpdatesProvider.php (1)

.vortex/installer/src/Utils/File.php (1)

• File (10-120)

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

• GitHub Check: build (0)
• GitHub Check: build (1)
• GitHub Check: vortex-test-deployment (0)
• GitHub Check: vortex-test-workflow (1)
• GitHub Check: vortex-test-deployment (1)
• GitHub Check: vortex-test-workflow (2)
• GitHub Check: vortex-test-workflow (3)
• GitHub Check: vortex-test-workflow (0)

🔇 Additional comments (11)

.github/workflows/update-dependencies.yml (2)

1-1: LGTM: Workflow name updated correctly.

The workflow name has been updated from "Dependency updates" to "Update dependencies" to align with the standardization effort.

---

14-14: LGTM: Job identifier updated correctly.

The job identifier has been renamed from deps-updates to update-dependencies which maintains consistency with the overall renaming effort.

.vortex/installer/src/Prompts/Handlers/DependencyUpdatesProvider.php (3)

29-29: LGTM: GitHub Actions workflow detection updated correctly.

The file existence check has been updated to look for the renamed workflow file .github/workflows/update-dependencies.yml.

---

33-33: LGTM: CircleCI job detection updated correctly.

The content search has been updated to look for the renamed job identifier update-dependencies in the CircleCI configuration.

---

54-54: LGTM: Cleanup logic updated correctly.

The file removal operation has been updated to target the renamed workflow file .github/workflows/update-dependencies.yml.

.vortex/installer/tests/Unit/PromptManagerTest.php (3)

8-8: Unrelated changes detected.

The addition of the Internal import and the CoversClass annotations appear to be unrelated to the dependency update renaming effort described in the PR summary and AI summary.

Also applies to: 54-79

Likely an incorrect or invalid review comment.

---

674-674: LGTM: Test data updated for GitHub Actions workflow.

The test data correctly references the renamed workflow file .github/workflows/update-dependencies.yml.

---

686-686: LGTM: Test data updated for CircleCI job name.

The test data correctly uses the renamed job identifier update-dependencies for CircleCI configuration testing.

.circleci/config.yml (3)

110-110: LGTM: Parameter renamed consistently.

The parameter has been correctly renamed from run_deps_updates to run_update_dependencies.

---

411-411: LGTM: Job renamed consistently.

The job identifier has been correctly renamed from deps-updates to update-dependencies.

---

672-672:

Details

✅ Verification successful

Verify all references have been updated consistently.

The workflow names and job references have been updated correctly. However, please verify that no old references to deps-updates or deps_updates remain in the codebase.

Also applies to: 683-686

---

🏁 Script executed:

#!/bin/bash
# Description: Search for any remaining references to the old naming convention
# Expected: No matches should be found

echo "==> Searching for old 'deps-updates' references..."
rg -i "deps-updates" --type yaml --type php --type json --type md

echo "==> Searching for old 'deps_updates' references..."
rg -i "deps_updates" --type yaml --type php --type json --type md

echo "==> Searching for old workflow filename references..."
rg -i "deps-updates\.yml" --type yaml --type php --type json --type md

echo "==> Verifying new references are present..."
rg -i "update-dependencies" --type yaml --type php | head -10

Length of output: 714

---

All deprecated dependency-update references have been removed

No occurrences of deps-updates or deps_updates remain in the repository, and the new update-dependencies job is defined in .circleci/config.yml (line 672).

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.75%. Comparing base (8ff142b) to head (d8126a3).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #1706      +/-   ##
===========================================
+ Coverage    70.59%   71.75%   +1.16%     
===========================================
  Files           76       76              
  Lines         4366     4366              
===========================================
+ Hits          3082     3133      +51     
+ Misses        1284     1233      -51     

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