Skip to content

chore(deps): bump platform MinimumVersionTag to v4.12.0-alpha.1#4103

Open
loft-bot wants to merge 1 commit into
mainfrom
update-platform-version-tag/v4.12.0-alpha.1
Open

chore(deps): bump platform MinimumVersionTag to v4.12.0-alpha.1#4103
loft-bot wants to merge 1 commit into
mainfrom
update-platform-version-tag/v4.12.0-alpha.1

Conversation

@loft-bot

@loft-bot loft-bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Bumps MinimumVersionTag to the new Platform release v4.12.0-alpha.1.


Note

Medium Risk
Changes the minimum Platform version gate used for compatibility resolution; scope is small but affects which Platform versions vCluster accepts.

Overview
Raises the minimum supported Loft Platform version from v4.10.3 to v4.12.0-alpha.1 in pkg/platform/version.go.

That constant drives MinimumVersion and is used when resolving compatible Platform releases (e.g. LatestCompatibleVersion fallbacks and semver checks against GitHub loft-sh/loft tags), so vCluster will treat Platform 4.12.0-alpha.1 as the new floor.

Reviewed by Cursor Bugbot for commit aaaae71. Bugbot is set up for automated code reviews on this repo. Configure here.

@loft-bot
loft-bot requested a review from a team as a code owner July 20, 2026 22:37
@github-actions

github-actions Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

E2E Ginkgo Tests

Status Commit Run
Passed aaaae7186371361d61a53c0f3efcc1b494336aa2 View run #29852702161

@Piotr1215

Copy link
Copy Markdown
Contributor

<!-- chore-triage-bot verdict=NEEDS-REVIEW merge=blocked -->
Triage verdict: NEEDS-REVIEW

Clean single-line bump of MinimumVersionTag (v4.10.3 -> v4.12.0-alpha.1). Checked loft-enterprise releases: latest stable is v4.11.0, not semver-GTE v4.12.0-alpha.1 (no stable release above target). LatestCompatibleVersion's stable-only filter finds nothing eligible and falls back to MinimumVersionTag itself, so default installs would resolve to this alpha. Same risk class as PR #4090.


Generated by Claude Code

@loft-bot
loft-bot force-pushed the update-platform-version-tag/v4.12.0-alpha.1 branch from 7de76ab to aaaae71 Compare July 21, 2026 17:22

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit aaaae71. Configure here.

Comment thread pkg/platform/version.go

var (
MinimumVersionTag = "v4.10.3"
MinimumVersionTag = "v4.12.0-alpha.1"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Prerelease minimum breaks release validation

High Severity

The MinimumVersionTag update to v4.12.0-alpha.1 conflicts with the release workflow's check_minimum_version_tag job, which expects a stable version. This causes stable vCluster tag releases to fail the check, blocking the publish job.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit aaaae71. Configure here.

Comment thread pkg/platform/version.go

var (
MinimumVersionTag = "v4.10.3"
MinimumVersionTag = "v4.12.0-alpha.1"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Default latest resolves to alpha

High Severity

Setting MinimumVersionTag to v4.12.0-alpha.1 makes the minimum version higher than the latest stable release. Consequently, LatestCompatibleVersion returns this alpha tag, causing vcluster platform start to deploy a pre-release by default instead of the latest stable platform.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit aaaae71. Configure here.

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.

2 participants