Skip to content

fix: install Quint in release-verify gate - #16

Merged
abienkowski merged 1 commit into
mainfrom
fix/release-install-quint
Aug 18, 2026
Merged

fix: install Quint in release-verify gate#16
abienkowski merged 1 commit into
mainfrom
fix/release-install-quint

Conversation

@abienkowski

Copy link
Copy Markdown
Collaborator

Problem

After #15 unblocked npm ci, the Release workflow's release-verify job now fails at the make release-verify step:

Error: Cannot find module '/home/runner/.hermes/node/lib/node_modules/@informalsystems/quint/dist/src/cli.js'
make[1]: *** [Makefile:67: typecheck] Error 1

make release-verify runs make typecheck and make verify, both of which invoke Quint. The job never installed Quint, so the Makefile's QUINT fallback (node $HOME/.hermes/...) pointed at a non-existent path and crashed — blocking version/release-*/publish-release.

Fix

Install Quint globally before the gate, mirroring the CI quint job (npm install -g @informalsystems/quint).

Verification

Part of epic #4; unblocks #6 and #8.

make release-verify runs 'make typecheck' and 'make verify', which invoke
Quint. The release-verify job never installed Quint, so the Makefile's QUINT
fallback pointed at a non-existent ~/.hermes path and typecheck crashed with
MODULE_NOT_FOUND, blocking the release pipeline. Install Quint globally
before the gate, mirroring the CI quint job.
@abienkowski
abienkowski merged commit d02518e into main Aug 18, 2026
6 checks passed
@abienkowski
abienkowski deleted the fix/release-install-quint branch August 18, 2026 11:05
abienkowski added a commit that referenced this pull request Aug 18, 2026
The publish-release job has no checkout step, so gh CLI cannot infer the
target repository from git context:

  failed to run git: fatal: not a git repository (or any of the parent
  directories): .git

This was the third and final blocker in the release pipeline (after #15's
npm ci fix and #16's Quint install fix). v0.2.7 was manually published via
'gh release edit' after confirming all its artifacts (Go/Rust/TS
binaries+archive, 6 SBOMs, Cosign signatures, public GHCR images) were
already valid. This fix ensures the *next* release (v0.2.8+) auto-publishes
without manual intervention.
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