feat(gui): Add alpha/beta release stage badge (#512) by amiable-dev · Pull Request #513 · amiable-dev/conductor

amiable-dev · 2026-03-08T00:10:42Z

Summary

Add [ALPHA] badge next to "CONDUCTOR" in TitleBar with amber block stamp styling
Badge shows ALPHA (amber) or BETA (blue), hidden entirely for production releases
Centralise release stage as semver pre-release suffix in workspace Cargo.toml (4.37.0-alpha)
Sync tauri.conf.json version to 4.37.0-alpha (also fixes Version numbers stale — tauri.conf.json not synced with workspace version #470 stale version)
StatusBar and SettingsPanel automatically display -alpha suffix via getVersion()
Add release-stage.ts utility with parseReleaseStage() function
16 tests: 8 utility tests + 8 TitleBar component tests (3 new badge tests)

Transition mechanism

Update one value to change stage:

Stage	`Cargo.toml`	`tauri.conf.json`	Badge
Alpha	`4.37.0-alpha`	`4.37.0-alpha`	Amber
Beta	`4.37.0-beta`	`4.37.0-beta`	Blue
Prod	`4.37.0`	`4.37.0`	Hidden

Closes #512
Fixes #470

Test plan

release-stage.test.ts — 8 tests for parseReleaseStage (alpha, beta, prod, edge cases)
TitleBar.test.ts — alpha badge renders, beta badge renders, no badge for production
Full frontend suite passes (725 tests, 47 files)
Rust workspace tests pass (conductor-core, conductor-daemon, conductor-gui --lib)
Manual: verify TitleBar shows CONDUCTOR [ALPHA] in Tauri dev server
Manual: verify StatusBar shows v4.37.0-alpha
Manual: verify Settings About shows Version 4.37.0-alpha

Generated with Claude Code

- Add [ALPHA] badge next to CONDUCTOR logo in TitleBar with amber styling - Badge shows ALPHA (amber) or BETA (blue), hidden for production releases - Centralise release stage as semver pre-release suffix in workspace Cargo.toml - Sync tauri.conf.json version to 4.37.0-alpha (also fixes #470 stale version) - StatusBar and SettingsPanel auto-display version with -alpha suffix via getVersion() - Add release-stage.ts utility with parseReleaseStage() and releaseStageBadgeClass() - Add 14 tests: 11 utility tests + 3 TitleBar badge rendering tests Closes #512 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Copilot

Pull request overview

Adds an explicit alpha/beta release-stage indicator to the GUI and aligns version strings so pre-release suffixes (e.g., -alpha) show consistently across the app.

Changes:

Introduces parseReleaseStage() utility + unit tests to derive alpha | beta | null from a semver string.
Updates TitleBar to fetch the app version via Tauri and conditionally render an ALPHA/BETA badge with stage-specific styling.
Bumps workspace + Tauri app versions to 4.37.0-alpha (and updates Cargo.lock accordingly) to address the previously stale GUI version.

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
conductor-gui/ui/src/lib/utils/release-stage.ts	New helper to parse release stage from semver strings.
conductor-gui/ui/src/lib/utils/release-stage.test.ts	Unit tests for `parseReleaseStage()` behavior and edge cases.
conductor-gui/ui/src/lib/components/TitleBar.svelte	Adds release-stage badge derived from `getVersion()` on mount.
conductor-gui/ui/src/lib/components/TitleBar.test.ts	Mocks `getVersion()` and adds coverage for alpha/beta/prod badge rendering.
conductor-gui/src-tauri/tauri.conf.json	Updates Tauri app version to `4.37.0-alpha` for correct `getVersion()` output.
Cargo.toml	Sets workspace version to `4.37.0-alpha`.
Cargo.lock	Updates workspace crate versions to match the new pre-release version.

You can also share your feedback on Copilot code review. Take the survey.

Copilot · 2026-03-08T00:18:31Z

conductor-gui/ui/src/lib/utils/release-stage.test.ts

+    expect(parseReleaseStage('4.37.0-snapshot')).toBe(null);
+  });
+
+  it('handles version with build metadata after stage', () => {


The test description says "build metadata" but the sample version uses a SemVer pre-release identifier ("-alpha.1"), not build metadata (which would be "+..." per SemVer). Renaming this test to reflect what it's actually asserting would avoid confusion for future maintenance.

Suggested change

it('handles version with build metadata after stage', () => {

it('handles version with dotted pre-release identifier', () => {

Copilot · 2026-03-08T00:18:32Z

conductor-gui/ui/src/lib/components/TitleBar.svelte

+  import { getVersion } from '@tauri-apps/api/app';
  import { deviceBindingsStore, profileStore } from '$lib/stores.js';
  import { workspaceView, WORKSPACE_VIEWS } from '$lib/stores/workspace.js';
+  import { parseReleaseStage } from '$lib/utils/release-stage.ts';


This Svelte codebase appears to import utilities without file extensions (e.g., "$lib/utils/diff-helpers"). Importing with an explicit ".ts" extension here is inconsistent and can cause tooling/resolution differences between TS/Vite setups. Consider switching to "$lib/utils/release-stage" to match existing imports.

Suggested change

import { parseReleaseStage } from '$lib/utils/release-stage.ts';

import { parseReleaseStage } from '$lib/utils/release-stage';

Copilot · 2026-03-08T00:18:32Z

conductor-gui/ui/src/lib/utils/release-stage.ts

+ * Single source of truth: the pre-release suffix in Cargo.toml workspace version
+ * (e.g., "4.37.0-alpha"). Tauri's getVersion() reads from tauri.conf.json which
+ * must be kept in sync.


The header comment calls Cargo.toml the "single source of truth" but the UI actually reads its version via Tauri getVersion() (tauri.conf.json). With the current changes, keeping these in sync is still a manual process and can regress (the underlying problem in #470). Consider adding an automated guard (e.g., CI check or a prebuild script) that fails if tauri.conf.json's version differs from the workspace Cargo.toml version.

Suggested change

* Single source of truth: the pre-release suffix in Cargo.toml workspace version

* (e.g., "4.37.0-alpha"). Tauri's getVersion() reads from tauri.conf.json which

* must be kept in sync.

* This helper is agnostic about where the version string comes from; it simply

* inspects the pre-release suffix (e.g., "4.37.0-alpha" or "4.37.0-beta") to

* determine the release stage. Callers are responsible for ensuring version

* values are consistent across Cargo.toml, tauri.conf.json (used by Tauri's

* getVersion()), and any other sources.

- Fix test name: "build metadata" → "dotted pre-release identifier" (correct SemVer terminology) - Drop .ts extension from import to match codebase convention - Reword doc comment to not overpromise "single source of truth" when sync is manual Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Copilot

Pull request overview

Copilot reviewed 6 out of 7 changed files in this pull request and generated 4 comments.

You can also share your feedback on Copilot code review. Take the survey.

Copilot · 2026-03-08T00:29:02Z

conductor-gui/ui/src/lib/components/TitleBar.svelte

+    padding: 2px 6px;
+    border-radius: var(--radius-sm);
+    color: var(--bg-app);
+    margin-left: 8px;


.titlebar-left already uses gap: 12px, but the badge also adds margin-left: 8px. With both, the spacing between “CONDUCTOR” and the badge becomes gap + margin-left (20px). Consider removing the extra margin (or adjusting the container gap) so spacing is controlled in one place.

Suggested change

margin-left: 8px;

Copilot · 2026-03-08T00:29:03Z

Cargo.toml

 [workspace.package]
-version = "4.37.0"
+version = "4.37.0-alpha"
 edition = "2024"


This change still leaves the app version duplicated between the workspace Cargo.toml and src-tauri/tauri.conf.json. Since GUI version displays read from Tauri’s getVersion(), the drift problem from #470 can recur unless there’s an automated sync/CI guard; consider adding a pre-build script (or CI check) that updates/validates tauri.conf.json from the workspace version so changing stage/version is truly single-source-of-truth.

Copilot · 2026-03-08T00:29:03Z

conductor-gui/ui/src/lib/utils/release-stage.test.ts

+ */
+
+import { describe, it, expect } from 'vitest';
+import { parseReleaseStage } from './release-stage.ts';


parseReleaseStage is imported with a .ts extension here, but the other util tests in this directory consistently import sibling modules without file extensions (e.g. ./diff-helpers). Using an extension here makes imports inconsistent and can complicate refactors/TS path settings; align this import style with the rest of the test suite.

Suggested change

import { parseReleaseStage } from './release-stage.ts';

import { parseReleaseStage } from './release-stage';

Copilot · 2026-03-08T00:29:03Z

conductor-gui/ui/src/lib/components/TitleBar.test.ts

+    // Give Svelte a tick to update
+    await new Promise(r => setTimeout(r, 50));
+    expect(screen.queryByText('ALPHA')).toBeNull();
+    expect(screen.queryByText('BETA')).toBeNull();


This test uses an arbitrary setTimeout(50) to wait for the badge to disappear. That kind of sleep tends to be flaky across environments; prefer asserting absence via vi.waitFor (or Svelte tick) so the test synchronizes on actual DOM state rather than timing.

Suggested change

// Give Svelte a tick to update

await new Promise(r => setTimeout(r, 50));

expect(screen.queryByText('ALPHA')).toBeNull();

expect(screen.queryByText('BETA')).toBeNull();

// Wait for Svelte to update DOM and ensure no release stage badge is shown

await vi.waitFor(() => {

expect(screen.queryByText('ALPHA')).toBeNull();

expect(screen.queryByText('BETA')).toBeNull();

}, { timeout: 2000 });

- Remove redundant margin-left on .release-stage (parent gap handles spacing) - Drop .ts extension from test import to match codebase convention - Replace setTimeout with vi.waitFor in production badge test to avoid flakiness - Version drift CI guard already tracked in #515 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

amiable-dev requested a review from Copilot March 8, 2026 00:14

Copilot started reviewing on behalf of amiable-dev March 8, 2026 00:15 View session

Copilot AI reviewed Mar 8, 2026

View reviewed changes

amiable-dev requested a review from Copilot March 8, 2026 00:25

amiable-dev mentioned this pull request Mar 8, 2026

chore: Add CI guard to keep tauri.conf.json version in sync with Cargo.toml #515

Open

3 tasks

Copilot started reviewing on behalf of amiable-dev March 8, 2026 00:25 View session

Copilot AI reviewed Mar 8, 2026

View reviewed changes

amiable-dev merged commit d523b2f into main Mar 8, 2026
11 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat(gui): Add alpha/beta release stage badge (#512)#513

feat(gui): Add alpha/beta release stage badge (#512)#513
amiable-dev merged 3 commits intomainfrom
feat/512-release-stage-badge

amiable-dev commented Mar 8, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Mar 8, 2026

Uh oh!

Copilot AI Mar 8, 2026

Uh oh!

Copilot AI Mar 8, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Mar 8, 2026

Uh oh!

Copilot AI Mar 8, 2026

Uh oh!

Copilot AI Mar 8, 2026

Uh oh!

Copilot AI Mar 8, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	it('handles version with build metadata after stage', () => {
	it('handles version with dotted pre-release identifier', () => {

	import { parseReleaseStage } from '$lib/utils/release-stage.ts';
	import { parseReleaseStage } from '$lib/utils/release-stage';

- * Single source of truth: the pre-release suffix in Cargo.toml workspace version
- * (e.g., "4.37.0-alpha"). Tauri's getVersion() reads from tauri.conf.json which
- * must be kept in sync.
+ * This helper is agnostic about where the version string comes from; it simply
+ * inspects the pre-release suffix (e.g., "4.37.0-alpha" or "4.37.0-beta") to
+ * determine the release stage. Callers are responsible for ensuring version
+ * values are consistent across Cargo.toml, tauri.conf.json (used by Tauri's
+ * getVersion()), and any other sources.

	import { parseReleaseStage } from './release-stage.ts';
	import { parseReleaseStage } from './release-stage';

Conversation

amiable-dev commented Mar 8, 2026

Summary

Transition mechanism

Test plan

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Mar 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Mar 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 8, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants