task: #3622591 Back to DEV

Summary

Varbase Project 11.0.9 is released, so the 11.0.x branch goes back to DEV.

• composer.json: "version" 11.0.9 → 11.0.x-dev.
• composer.json: vardot/varbase and vardot/varbase-patches ~11.0.0 → 11.0.x-dev.
• Removed composer.lock and patches.lock.json.

The released constraints and the committed lock files belong to the release tag, not to the development branch: on 11.0.x the branch has to resolve against the development versions of Varbase and Varbase Patches, and a committed lock would pin it to the released set.

This is the same shape as the Back to DEV commit after the 11.0.8 release (e000674).

Issue

https://www.drupal.org/project/varbase_project/issues/3622591 — Plan: release Varbase Project 11.0.9

Release facts

• Annotated tag 11.0.9 (72d37c7) at commit 7236346 on 11.0.x.
• Tag pipeline 969091 green, 35/35 jobs.
• Pushed to drupal.org and mirrored to github.com/Vardot/varbase-project.
• Release node published: https://www.drupal.org/project/varbase_project/releases/11.0.9

Notes

• Only composer.json, composer.lock and patches.lock.json are touched. No other file is in this merge request.
• The composer CI job resolves from composer.json rather than from a committed lock, so it now resolves vardot/varbase and vardot/varbase-patches at 11.0.x-dev. Whatever the pipeline on this branch reports is the observed behaviour, and it is stated rather than assumed here.

AI-Generated: Yes

Checkpoints:

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