Skip to content

Conversation

@hwittenborn
Copy link

This fixes #573. It also would be good practice to support any developers who are genuinely using a bleeding edge version of Docker Compose.

This fixes TibixDev#573. It also would be good practice to support any developers who are genuinely using a bleeding edge version of Docker Compose.
Copilot AI review requested due to automatic review settings December 22, 2025 12:58
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds support for detecting development versions of Docker Compose by recognizing "dev" as a valid version string. This addresses issue #573 and ensures that developers using bleeding-edge Docker Compose builds can use the application.

Key changes:

  • Added detection for "dev" version strings in Docker Compose version output
  • Development builds are assumed to be v2+ compatible

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

if (versionMatch) {
const majorVersion = Number.parseInt(versionMatch[1].split(".")[0], 10);
specs.dockerComposeInstalled = majorVersion >= 2;
} else if (dockerComposeOutput.includes("dev")) {
Copy link

Copilot AI Dec 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The check dockerComposeOutput.includes("dev") is too broad and could produce false positives. For example, it would match "Docker Compose version 2.35.1 - developer edition" or any output containing the substring "dev" anywhere. Consider using a more specific pattern like /version\s+(dev|v?dev)\b/i.test(dockerComposeOutput) to match "dev" only when it appears as a standalone version string.

Suggested change
} else if (dockerComposeOutput.includes("dev")) {
} else if (/version\s+(dev|v?dev)\b/i.test(dockerComposeOutput)) {

Copilot uses AI. Check for mistakes.
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think checking for dev itself is fine, though I'm more than fine with changing that if need be.

Copy link
Owner

@TibixDev TibixDev Jan 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we do .endsWith perhaps and see if that still works? Would be a bit cleaner.

@auri-f5bde6
Copy link
Contributor

I think it would be better if the button becomes "continue anyway" and pop up a dialog about potential problems if the version doesn't match.

if (versionMatch) {
const majorVersion = Number.parseInt(versionMatch[1].split(".")[0], 10);
specs.dockerComposeInstalled = majorVersion >= 2;
} else if (dockerComposeOutput.includes("dev")) {
Copy link
Owner

@TibixDev TibixDev Jan 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we do .endsWith perhaps and see if that still works? Would be a bit cleaner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Newest docker compose release 5.0.0 not recognized as >v2

3 participants