Plan: release Varbase Project 11.0.8

Problem/Motivation

Plan for the next Varbase Project Template release, 11.0.8, following #3621788 for 11.0.7.

There is nothing to release yet. Branch 11.0.x HEAD is the same commit as tag 11.0.7 (1747aa885a5c, tagged 2026-09-08): zero commits and zero changed files between them. 11.0.8 is blocked on real changes landing on 11.0.x and on the branch going green again.

Two things are also still open from 11.0.7:

• The Back to DEV for 11.0.7 was never done. composer.json on 11.0.x still reads version 11.0.7, the drupal/varbase* cross dependency constraints are still pinned at ~11.0.0, and composer.lock and patches.lock.json are still committed. Every earlier release (11.0.6, 11.0.5, 10.1.4, 10.1.3, 9.2.2, 9.2.0) has a matching Back to DEV merge request, 11.0.7 has none. There are currently 0 open merge requests on the project.
• CI is red on the release commit. Branch pipeline 953823, on the 11.0.7 commit, failed on Create reports and Install Varbase, both with allow_failure: false. Tag pipeline 953826, on tag 11.0.7, failed on Create reports, which is the job that produces the Automated Functional Acceptance Testing report, so the report link on the published 11.0.7 release node is likely broken. The last green branch pipeline was 953544, on commit 1be6edea, the commit before the 11.0.7 release commit.

Steps to reproduce

1. Compare tag 11.0.7 with branch 11.0.x on git.drupalcode.org: no commits and no changed files between them.
2. Read composer.json on 11.0.x: version 11.0.7, cross dependency constraints at ~11.0.0, and composer.lock plus patches.lock.json still committed.
3. Open pipelines 953823 (branch) and 953826 (tag): both failed.
4. Open the 11.0.7 release node and follow the Automated Functional Acceptance Testing report link.

Proposed resolution

Do the outstanding 11.0.7 work first, get 11.0.x green, and only then run the normal 11.0.8 release flow. Order matters: no tag is cut off a red branch, and no version bump is done on a branch that was never returned to DEV.

Remaining tasks

Before 11.0.8 can be tagged, in this order:

1. ❌ Back to DEV for 11.0.7 on 11.0.x: set composer.json version to the dev value the series uses, restore the dev cross dependency constraints for the drupal/varbase* packages, and handle composer.lock and patches.lock.json per the project's own convention.
2. ❌ Fix CI on 11.0.x: the red Create reports job and the red Install Varbase job, so the branch pipeline is green again.
3. ❌ Re-check the 11.0.7 release node: the Automated Functional Acceptance Testing report link, since the job that produces it failed on the tag pipeline.
4. ❌ Then the normal 11.0.8 flow: version bump merge request, green CI gated tag, release node, change issue flips, Back to DEV.

Checkpoints:

• ✅ File an issue
• ❌ Addition/Change/Update/Fix
• ❌ Testing to ensure no regression
• ❌ Automated unit/functional testing coverage
• ➖ Developer Documentation support
• ➖ User Guide Documentation support
• ➖ UX/UI designer responsibilities
• ➖ Accessibility and Readability
• ❌ Reviewed by a human
• ❌ Code review by maintainers
• ❌ Full testing and approval
• ❌ Credit contributors
• ❌ Review with the product owner
• ❌ Update Release Notes
• ❌ Release

User interface changes

• N/A

API changes

• N/A

Data model changes

• N/A

Release notes snippet

• N/A, nothing has landed on 11.0.x since 11.0.7. To be written once there are changes to ship.

Install with:

composer create-project drupal/varbase_project:~11 PROJECT_DIR_NAME --no-dev --no-interaction

AI-Generated: Yes