Skip to content

v0.5.68

Choose a tag to compare

@github-actions github-actions released this 17 Oct 01:48
· 18 commits to main since this release

Nothing in this release changes what conclave does. A dev-dependency bump and one test record. Installing it is optional.

The even-terminal pin records the version it is checked against

evenCompat.test.ts pins conclave's imitation of the Even Realities Terminal Mode protocol against the installed @evenrealities/even-terminal, because that protocol belongs to somebody else and changes without notice.

Three different numbers were in play, which is how it went unnoticed: the vendor installed on the machine that runs these tests was 0.8.1, the file recorded 0.10.4 as the version its claims had been verified against, and published was 0.10.5. So every green in that file was evidence about 0.8.1 while the file claimed 0.10.4.

The vendor is upgraded and the record now matches at 0.10.5. The drift notice did its whole job in between: with 0.10.5 installed and 0.10.4 recorded, the pin passed all thirteen claims and said "Every green in this file is evidence about 0.10.5, not 0.10.4." Green about the wrong version, named as such.

The record was not bumped because the tests passed. That would be the defect the pin exists to catch — asserting verification from a check that cannot see what it does not cover. The two bundles were diffed, and exactly one file differs: the vendor's own Codex adapter, which cut its idle unsubscribe from three minutes to thirty seconds, shortened its sweep, and added a discovery gate. conclave serves that protocol rather than driving Codex through it, so it implements none of that, and nothing the pin covers moved.

One thing worth knowing later, since the numbers look comparable and are not related: the vendor now unsubscribes idle sessions after thirty seconds. conclave's own linger values were chosen deliberately — sixty seconds for a run, thirty for a session — and are unchanged here. Anyone comparing the two should know they were not copied from each other.

A limitation of this kind of pin, stated: CI has no vendor installed, so the pin skips there — loudly, naming where it looked, which is deliberate. The claims are verified on a machine that has the vendor, and the recorded version is the artefact that says which one. A green CI run says nothing about them.

Dev dependency

@types/node to 26.6.3.