Skip to content

Publish the compatibility matrix on GitHub Pages - #18

Merged
bbatsov merged 3 commits into
mainfrom
matrix-page
Nov 3, 2026
Merged

bbatsov merged 3 commits into
mainfrom
matrix-page

Conversation

@bbatsov

@bbatsov bbatsov commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

The matrix gets a page of its own at https://nrepl.github.io/proof/, with the version of each server. The versions come from a new version snippet rather than describe, which gets them wrong for nbb, let-go and jank.

describe's versions can't be trusted for this: nbb says TODO, let-go
says 1.0 while it's 1.13.0, and jank says jank-0.1-alpha whatever the
build. So a profile can have a version snippet now, which proof
evaluates in a session of its own before the checks. The text and JSON
reports and the Markdown matrix show what it evaluates to after the
name of the server.

The bundled profiles that install the latest release (or main) get
one. nREPL and ClojureCLR keep the version they pin in their names,
and jank has no way to tell its version from the code.
So far the matrix lived in the summary of the Compatibility workflow,
which few people would find. Now proof matrix -html builds it as a web
page, where hovering over a check shows why it matters and hovering
over a verdict shows what went wrong, and the workflow publishes it
from main.

The page gets published only when every server's job succeeded, as a
page that's a day old beats one that's missing a server. The runs
build proof with the latest Go and the whole history, so the reports
(and the page) say which commit of proof made them.

The table is written without html/template, which would make the
binary 2 MB bigger. A check that only a later report has now goes with
the rest of its group, in the Markdown matrix as well.
The matrix gets a page of its own, along with nbb, let-go and two more clients. The upstream section catches up with what got merged and reported since 0.1.0.
@bbatsov
bbatsov merged commit b939992 into main Nov 3, 2026
5 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