task: #3622591 Back to DEV

Back to DEV after the Varbase Project 11.0.8 release, on the plan issue #3622591.

What this changes

• composer.json: version from 11.0.8 back to 11.0.x-dev.
• composer.json: vardot/varbase and vardot/varbase-patches from ~11.0.0 back to 11.0.x-dev.
• composer.lock deleted.
• patches.lock.json deleted.

yarn.lock stays tracked. Three files, nothing else.

Why

The release commit and the dev branch want opposite things from the same file.

A release tag ships committed composer.lock and patches.lock.json so that composer create-project installs from the lock with the solver skipped, which is what makes an install of 11.0.8 deterministic and identical for everyone.

The dev branch wants the opposite: no locks, so 11.0.x-dev resolves the current tip of each Varbase line and CI exercises what the next release will actually contain. Leaving version: 11.0.8 and the ~11.0.0 pins on the branch would mean 11.0.x-dev advertises itself as a released version and resolves to released dependencies, so nothing downstream would ever see the next release's code before it ships.

Composer resolution for vardot/varbase runs off the GitHub mirror, so 11.0.x-dev there is what dev consumers actually get. That makes landing this promptly after a release worth doing rather than letting it drift.

composer.json returns to blob 734c3e4, byte for byte the content it had before the release commit, so this is an exact round trip and not an approximation.

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