Removed generic private package used for testing from the root composer.json.

[AlexSkrypnyk]

Summary by CodeRabbit

• Tests
  • Updated test names and documentation to focus on "Package token" handling during the build process.
• Chores
  • Removed the "drevops/generic-private-package" dependency and its related repository entry.

[coderabbitai]

Walkthrough

This change updates a test method and its documentation in a workflow test to focus on "Package token" instead of "GitHub token" handling. Additionally, the composer configuration removes a private package dependency and its corresponding repository entry. No other logic or configuration is altered.

Changes

File(s)	Change Summary
.vortex/tests/phpunit/Functional/WorkflowTest.php	Renamed test method and doc comment from "GitHub token" to "Package token"; logic unchanged.
composer.json	Removed "drevops/generic-private-package" dependency and related VCS repository entry.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Possibly related PRs

• Added private package example. #1820: Renames a test and environment variable from GitHub token to Package token, aligning with this PR's focus on package token handling in tests and CI.

Poem

A token once for GitHub's gate
Now helps a package integrate.
Composer trims a line or two,
While tests get names that feel brand new.
With tidy code and cleaner rhyme,
This rabbit hops through review time! 🐇✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 phpcs (3.7.2)

.vortex/tests/phpunit/Functional/WorkflowTest.php

ERROR: Referenced sniff "Drupal" does not exist

Run "phpcs --help" for usage information

---

📜 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 0bc8d68 and 6239425.

📒 Files selected for processing (2)

• .vortex/tests/phpunit/Functional/WorkflowTest.php (1 hunks)
• composer.json (0 hunks)

💤 Files with no reviewable changes (1)

• composer.json

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: CR
PR: drevops/vortex#0
File: CLAUDE.md:0-0
Timestamp: 2025-07-18T15:00:28.327Z
Learning: Composer dependencies are updated automatically with compatibility checks via RenovateBot

Learnt from: AlexSkrypnyk
PR: drevops/vortex#1816
File: .docker/cli.dockerfile:72-76
Timestamp: 2025-07-23T01:16:30.963Z
Learning: In the Vortex project, unauthenticated Composer installs should be allowed, so GitHub token secrets should not be marked as `required=true` in Docker build mounts. The conditional check `if [ -s /run/secrets/github_token ]` is the preferred approach to allow builds to proceed without a token when needed.

.vortex/tests/phpunit/Functional/WorkflowTest.php (1)

Learnt from: AlexSkrypnyk
PR: #1816
File: .docker/cli.dockerfile:72-76
Timestamp: 2025-07-23T01:16:30.963Z
Learning: In the Vortex project, unauthenticated Composer installs should be allowed, so GitHub token secrets should not be marked as required=true in Docker build mounts. The conditional check if [ -s /run/secrets/github_token ] is the preferred approach to allow builds to proceed without a token when needed.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (13)

• GitHub Check: build (1)
• GitHub Check: build (0)
• GitHub Check: vortex-test-common
• GitHub Check: vortex-test-deployment (1)
• GitHub Check: vortex-test-workflow (3)
• GitHub Check: vortex-test-workflow (0)
• GitHub Check: vortex-test-workflow (2)
• GitHub Check: vortex-test-workflow (1)
• GitHub Check: vortex-test-deployment (0)
• GitHub Check: vortex-test-installer (8.2)
• GitHub Check: vortex-test-installer (8.4)
• GitHub Check: vortex-test-installer (8.3)
• GitHub Check: vortex-test-docs

🔇 Additional comments (1)

.vortex/tests/phpunit/Functional/WorkflowTest.php (1)

54-54: LGTM! Documentation updated to reflect the test's purpose.

The doc comment accurately reflects the test's focus on package token handling rather than GitHub-specific token handling.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/remove-private-package

---

🪧 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 generate unit tests to generate unit tests 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.

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 74.00%. Comparing base (2bfdfc7) to head (6239425).
Report is 5 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #1835      +/-   ##
===========================================
- Coverage    74.02%   74.00%   -0.03%     
===========================================
  Files           84       84              
  Lines         4813     4813              
  Branches        35       35              
===========================================
- Hits          3563     3562       -1     
- Misses        1250     1251       +1     

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