Skip to content

Conversation

@AlexSkrypnyk
Copy link
Member

@AlexSkrypnyk AlexSkrypnyk commented Oct 3, 2025

Summary by CodeRabbit

  • Chores
    • Upgraded CMS dependency to 1.2 for improved compatibility and stability.
    • Enabled additional Composer plugins (installers, core scaffold, recipe unpack, vendor hardening, HTTP discovery) while retaining existing merge-plugin behavior.
    • Set minimum stability to alpha to allow early-release packages during installation.
    • Improved installer configuration for more reliable project setup; no direct UI changes.

@coderabbitai
Copy link

coderabbitai bot commented Oct 3, 2025

Walkthrough

Updates an embedded Composer configuration in the Starter handler: bumps drupal/cms to ^1.2, adds multiple allow-plugins entries, sets minimum-stability to alpha, and preserves existing extra.merge-plugin settings.

Changes

Cohort / File(s) Summary of changes
Starter handler Composer config
.vortex/installer/src/Prompts/Handlers/Starter.php
Updated embedded composer.json: bumped drupal/cms from ^1.0 to ^1.2; added allow-plugins entries for composer/installers, drupal/core-composer-scaffold, drupal/core-recipe-unpack, drupal/core-vendor-hardening, and php-http/discovery; retained existing allow-plugins.wikimedia/composer-merge-plugin; set minimum-stability to alpha; preserved existing extra.merge-plugin settings.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

AUTOMERGE

Poem

A bump, a hop—my paws take flight,
Composer gates now open bright.
Plugins welcomed, alpha air,
Merge kept tidy with care.
Thump-thump—deploy into the night. 🐇✨

Pre-merge checks and finishing touches

✅ 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 accurately and succinctly summarizes the primary change by stating that the installer now correctly updates the composer.json for the Drupal CMS starter, matching the content of the diff without extraneous detail.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feature/fix-installer-not-merging-allow-plugins

📜 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 f4fd388 and c478884.

⛔ Files ignored due to path filters (1)
  • .vortex/installer/tests/Fixtures/install/starter_drupal_cms_profile/composer.json is excluded by !.vortex/installer/tests/Fixtures/**
📒 Files selected for processing (1)
  • .vortex/installer/src/Prompts/Handlers/Starter.php (1 hunks)
⏰ 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). (14)
  • GitHub Check: build (1)
  • GitHub Check: build (0)
  • GitHub Check: vortex-test-workflow (2)
  • GitHub Check: vortex-test-common
  • GitHub Check: vortex-test-workflow (0)
  • GitHub Check: vortex-test-workflow (4)
  • GitHub Check: vortex-test-workflow (3)
  • GitHub Check: vortex-test-workflow (1)
  • GitHub Check: vortex-test-deployment (1)
  • GitHub Check: vortex-test-deployment (0)
  • GitHub Check: vortex-test-installer (8.3)
  • GitHub Check: vortex-test-installer (8.2)
  • GitHub Check: vortex-test-installer (8.4)
  • GitHub Check: vortex-test-docs
🔇 Additional comments (2)
.vortex/installer/src/Prompts/Handlers/Starter.php (2)

96-96: LGTM: Version bump aligns with PR objectives.

The update to drupal/cms version ^1.2 is consistent with the PR's goal to fix the installer for Drupal CMS starter.


100-105: LGTM: Required plugin configurations added.

The allow-plugins entries for composer/installers, drupal/core-composer-scaffold, drupal/core-recipe-unpack, drupal/core-vendor-hardening, and php-http/discovery are standard requirements for Drupal CMS and necessary for proper installation.


Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions bot temporarily deployed to commit October 3, 2025 05:44 Inactive
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ce663ed and f4fd388.

📒 Files selected for processing (1)
  • .vortex/installer/src/Prompts/Handlers/Starter.php (1 hunks)
⏰ 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). (14)
  • GitHub Check: build (1)
  • GitHub Check: build (0)
  • GitHub Check: vortex-test-workflow (3)
  • GitHub Check: vortex-test-workflow (4)
  • GitHub Check: vortex-test-workflow (2)
  • GitHub Check: vortex-test-workflow (0)
  • GitHub Check: vortex-test-workflow (1)
  • GitHub Check: vortex-test-deployment (0)
  • GitHub Check: vortex-test-deployment (1)
  • GitHub Check: vortex-test-common
  • GitHub Check: vortex-test-installer (8.3)
  • GitHub Check: vortex-test-installer (8.4)
  • GitHub Check: vortex-test-installer (8.2)
  • GitHub Check: vortex-test-docs
🔇 Additional comments (2)
.vortex/installer/src/Prompts/Handlers/Starter.php (2)

100-106: LGTM! Comprehensive allow-plugins configuration.

The added plugin permissions are standard for Drupal CMS installations:

  • composer/installers: Handles custom install paths for Drupal packages
  • drupal/core-composer-scaffold: Scaffolds Drupal core files
  • drupal/core-recipe-unpack: Unpacks Drupal recipes (required for CMS)
  • drupal/core-vendor-hardening: Hardens vendor directory
  • php-http/discovery: HTTP client discovery

All entries are correctly set to TRUE and align with Drupal CMS ^1.2 requirements.


96-96: Approve drupal/cms ^1.2 bump. Verified 1.2.6 is the latest stable release with no breaking changes; ensure upgrade uses composer update --with-all-dependencies and run recipe unpack steps.

$cj->addConfigSetting('allow-plugins.php-http/discovery', TRUE);
$cj->addConfigSetting('allow-plugins.wikimedia/composer-merge-plugin', TRUE);

$cj->addProperty('minimum-stability', 'alpha');
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick | 🔵 Trivial

🧩 Analysis chain

Document the rationale for alpha minimum-stability.

Setting minimum-stability to alpha allows installation of unstable packages, which introduces risk. Please verify:

  • Is this required for drupal/cms ^1.2 or its dependencies?
  • Should this be conditional or temporary?
  • Are there specific alpha packages that necessitate this setting?

Consider adding a comment in the code explaining why alpha stability is required.


🏁 Script executed:

#!/bin/bash
# Description: Check if drupal/cms ^1.2 requires alpha stability or has alpha dependencies

# Check drupal/cms composer.json for stability requirements
curl -s "https://repo.packagist.org/p2/drupal/cms.json" | \
  jq '.packages["drupal/cms"][] | select(.version | startswith("1.2")) | {version, "minimum-stability": .["minimum-stability"], require}'

Length of output: 5289


Remove or document global minimum-stability: alpha

  • drupal/cms ^1.2 declares its pre-release deps with explicit @alpha/@beta flags, so this global setting isn’t needed—drop it or replace with prefer-stable: true.
  • If you must keep it, add a comment explaining which specific package(s) require alpha stability.
🤖 Prompt for AI Agents
.vortex/installer/src/Prompts/Handlers/Starter.php around line 108: the code
sets a global "minimum-stability: alpha" which is unnecessary for drupal/cms (it
uses explicit @alpha/@beta) and is risky; either remove the global
minimum-stability line entirely or replace it with "prefer-stable: true"; if you
must keep "minimum-stability: alpha" add a clear inline comment naming the
specific package(s) that require alpha and why, and ensure the composer output
prefers stable releases by adding prefer-stable: true.

@codecov
Copy link

codecov bot commented Oct 3, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 63.99%. Comparing base (ce663ed) to head (c478884).
⚠️ Report is 1 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #2041      +/-   ##
===========================================
+ Coverage    63.95%   63.99%   +0.03%     
===========================================
  Files           91       91              
  Lines         5637     5643       +6     
  Branches        44       44              
===========================================
+ Hits          3605     3611       +6     
  Misses        2032     2032              

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

@AlexSkrypnyk AlexSkrypnyk force-pushed the feature/fix-installer-not-merging-allow-plugins branch from f4fd388 to c478884 Compare October 3, 2025 07:11
@github-actions github-actions bot temporarily deployed to commit October 3, 2025 07:13 Inactive
@AlexSkrypnyk AlexSkrypnyk enabled auto-merge (rebase) October 6, 2025 02:34
@AlexSkrypnyk AlexSkrypnyk merged commit 3135f43 into develop Oct 6, 2025
39 of 40 checks passed
@AlexSkrypnyk AlexSkrypnyk deleted the feature/fix-installer-not-merging-allow-plugins branch October 6, 2025 02:40
@github-project-automation github-project-automation bot moved this from BACKLOG to Release queue in Vortex Oct 6, 2025
@AlexSkrypnyk AlexSkrypnyk added this to the 25.10.0 milestone Oct 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Released in 25.10.0

Development

Successfully merging this pull request may close these issues.

2 participants