Loading
task: #3621162 Back to DEV
Release plan issue: #3621162
Problem / Motivation
1.0.0-rc1 is tagged (commit d72991bc, tag object e6832373), so the release constraints are captured in the tag. The 1.0.x branch must now go back to development.
Proposed resolution
composer.json only, no other file:
version1.0.0-rc1->1.0.x-dev.- All 19
drupal/varbase_*_base/drupal/vartheme_bs5_educarerequirements~1.0.0->1.0.x-dev.
Deliberately untouched: drupal/core ^11.3, the 13 drupal/drupal_cms_* ~2, drupal/easy_email_express ~1, drupal/recipe_installer_kit ~1.
The rewrite was asserted at exactly 19 and the result re-parsed as JSON, because drupal/varbase_i18n_base is easy to miss: a varbase_[a-z_]+ pattern does not match the digits in i18n.
Remaining tasks
- Merge, automatically once the pipeline is green.
Checkpoints
- Follows the Drupal coding standards.
-
composer.jsonre-parsed as JSON after editing. - Exactly 19 cross-dependency rewrites asserted,
drupal/varbase_i18n_baseincluded. - The
1.0.0-rc1tag is unaffected: it keepsversion: 1.0.0-rc1and its 19 pinned releases. - Reviewed by a human.
- Code review by maintainers.
AI-Generated: Yes