What changed in Liskov
-
Login works on Windows
On Windows,
proof liskov loginopened a page that said your code was missing. It now opens the full link.Thanks to a design partner
-
Choosing an organization by name now tells you its slug
proof liskov organization useonly accepts an organization's slug or ID. If you type its display name, the CLI now tells you the matching slug and ID to use instead of only refusing.Thanks to a design partner
-
How to set a required secret before your first run
An Application's Secrets page lists nothing until a policy that declares the secret is published, so a required secret could not be set in advance. The GitHub guide now shows the way through: publish paused, set the secret, then resume.
Thanks to a design partner
-
The runtime SDK reference explains what job.id holds
job.idlooks like an object when you log it, but it is always a string. The runtime SDK reference now says so, and says to treat it as an opaque value.Thanks to a design partner
-
The GitHub deployment guide matches what you actually see
The guide to deploying from GitHub named an old CLI plugin version, a log line and a field name that no longer exist. It now names the current plugin, the real "Pinned" log line, the
manifestValidfield and the current runtime, and shows how to check which plugin version is installed.Thanks to a design partner
-
Anyone can sign in with GitHub
"Continue with GitHub" showed a GitHub 404 page to anyone outside our own organization, so new users could not sign in that way. It now works for every GitHub account.
Thanks to a design partner
-
The Run panel no longer shows a false eligibility error
For an Application that runs once, the Run panel could show a red "Launch eligibility evidence is unavailable" while the run was fine. It now reads the Application's policy explanation and shows its real state.
Thanks to a customer