Skip to content

[vscode] Test against the latest Iris canary - #5

Merged
purefunctor merged 1 commit into
mainfrom
vscode/test-iris-canaries
Sep 12, 2026
Merged

[vscode] Test against the latest Iris canary#5
purefunctor merged 1 commit into
mainfrom
vscode/test-iris-canaries

Conversation

@purefunctor

Copy link
Copy Markdown
Owner

Why

Extension changes should be exercised against both the latest stable Iris release and current language-server development. Hard-coding a canary tag would require an extension commit for every Iris commit.

Depends on purefunctor/purescript-iris#504, which publishes the canary releases consumed here. Merge that PR first so this workflow can resolve its initial canary.

What changed

  • Preserve the existing stable Iris platform and VS Code-version matrix.
  • Add focused Linux coverage against stable VS Code and the latest published Iris canary.
  • Resolve the newest non-draft v<version>-dev.<12-hex-revision> prerelease from the Iris Releases API at job runtime.
  • Pin that exact tag for installation and verify the executable reports the matching version before running integration tests.

No IRIS_VERSION is committed, and Iris does not need cross-repository credentials or push-triggered integration.

Verification

  • npm run check
  • npx prettier --check .github/workflows/checks.yml
  • actionlint .github/workflows/checks.yml
  • Resolver fixture covering stable releases, drafts, release candidates, and multiple canaries
  • git diff --check

A live canary installation cannot run until purefunctor/purescript-iris#504 publishes the first canary.

@purefunctor
purefunctor merged commit 47c1777 into main Sep 12, 2026
5 of 14 checks passed
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