ci: build darwin-x64 on macos-latest runner + bump version 0.1.0#134
Merged
Conversation
macos-13 (Intel Mac) runners are queued indefinitely on GitHub Actions as of 2026-05 — every publish-extension run since the v0.0.3 tag push got stuck on darwin-x64 alone (no allocation, queue never moves). Apple deprecated Intel Macs in 2024-2025; GitHub reduced runner capacity for macos-13 accordingly. Switch the darwin-x64 row's runner to macos-latest (currently macos-14 = arm64). Our binary is pure JS bundled via esbuild — no native Intel compilation step. The vsce package step still passes '--target darwin-x64' so the produced .vsix is marked for darwin-x64 marketplace install correctly. Intel Mac users download the same JS payload and execute it via their local Node runtime — the shebang shim works on Intel Macs as well as Apple Silicon. Result: darwin-x64 allocates instantly on macos-14 like its darwin-arm64 sibling, the full matrix completes, the publish job triggers, the release lands on Open VSX.
First real public release on Open VSX. v0.0.x was internal alpha during the v2 plan iteration; v0.1.0 marks the feature-complete sidebar monitor + cooperative-by-default + cross-platform release ready for outside users. Marketplace tag will be extension-v0.1.0.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two changes for the first real marketplace publish:
1. CI workflow fix — every
publish-extensionrun since the v0.0.3 tag push got stuck on thedarwin-x64build job. It requested amacos-13Intel Mac runner that GitHub Actions never allocated. Six runs across the past hour show darwin-x64 with status=queued, runner_name=null, never started. Apple deprecated Intel Macs in 2024-2025 and GitHub reduced macos-13 runner capacity to effectively zero free-tier availability.Fix: switch the darwin-x64 row from
macos-13tomacos-latest(macos-14 = arm64). Our binary is pure JavaScript bundled via esbuild — no Intel-specific native compilation. The vsce package step still passes--target darwin-x64so the produced .vsix is correctly marketed for Intel Mac. Intel Mac users download the same JS payload and execute it via local Node — the shebang shim works on both architectures.2. Version bump 0.0.3 → 0.1.0 — first real public marketplace release. v0.0.x was internal alpha; v0.1.0 marks feature-complete sidebar monitor + cooperative-by-default + cross-platform.
After merge
git tag -a extension-v0.1.0 -m "..." && git push origin extension-v0.1.0ovsx publishper platform — 5 .vsix files land on Open VSX🤖 Generated with Claude Code