fix: support docker-compose >= 2.x

[sjinks]

Description

This pull request updates the Docker Compose version check in the validateDockerInstalled function to be more inclusive of valid versions. Current version of docker-compose standalone binary is 5.x; our code checks for ^2.0.0 and, therefore, fails on 5.x.

Dependency validation update:

• Relaxed the version constraint for Docker Compose in validateDockerInstalled to allow any version 2.0.0 or higher, instead of only versions matching the ^2.0.0 range. (src/lib/dev-environment/dev-environment-lando.ts)

Changelog Description

Fixed

• Dev Environment: allow docker-compose newer than 2.x

Pull request checklist

• Update SETUP.md with any new environmental variables.
• Update the documentation.
• Manually test the relevant changes.
• Follow the pull request checklist
• Add/update automated tests as needed.

New release checklist

• Automated tests pass.
• The Preparing for release checklist is completed.

Steps to Test

Install the docker-compose binary from https://github.com/docker/compose/releases and ensure that dev env works.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull request overview

This PR fixes a Docker Compose version validation issue that was preventing users from using docker-compose versions 3.x and higher (including the current 5.x). The validation was using ^2.0.0 which only allows 2.x versions, but the error message and intended behavior was to support any version 2.0.0 or higher.

• Changed the semver range from ^2.0.0 (which matches >=2.0.0 <3.0.0) to >=2.0.0 (which matches 2.0.0 and all higher versions)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.