Skip to content

Install versioned compiler releases and allow pinned version selection - #150

Draft
Frotty wants to merge 2 commits into
masterfrom
codex/versioned-compiler-releases
Draft

Frotty wants to merge 2 commits into
masterfrom
codex/versioned-compiler-releases

Conversation

@Frotty

@Frotty Frotty commented Oct 8, 2026

Copy link
Copy Markdown
Member

The compiler updater currently follows nightly commit hashes, so any master merge becomes an update. This switches installation and update discovery to published stable vMAJOR.MINOR.PATCH releases, displays semantic compiler versions, and adds Wurst: Choose Compiler Version to the Command Palette and status menu.

Automatic update checks compare semantic versions. The picker supports upgrades and downgrades through the existing staged installer and cross-window installation lock. An explicit version choice stays pinned; Follow latest stable resumes ordinary update offers. Existing nightly installations get a stable-release migration offer, and missing stable platform releases are reported clearly.

Rollout: merge the companion compiler workflow and publish the first v2.0.0 compiler before releasing this extension. Until then, GitHub contains no stable compiler release to install. No live installation or release is changed by this draft.

Companion compiler draft: wurstscript/WurstScript#1383.

Validation: all npm test harnesses, TypeScript, full lint, diff checks and VSIX packaging pass. Behavioral coverage includes stable-release filtering, semantic ordering, exact platform assets, nightly migration, older-version selection, coordinated staging, pin persistence, failed installs retaining the pin, and following latest stable. Actual stable-release installation awaits publication of v2.0.0.

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.

1 participant