toolchain.version_older

The project is written for an earlier Jadpo release line than the jadpo checking it, and that jadpo can't run the earlier release instead.

Area 1, Project layout and modules; not declinable; the next step is usually the human's.

Why Jadpo refuses it

jadpo: in app.jadpo names the release line the project is written for. Normally the installed jadpo runs that line's release for you, fetching it once if it doesn't keep it. You see this error when it can't: you set JADPO_TOOLCHAIN=local, so it runs every command itself, or it couldn't fetch the release.

While Jadpo is at 0.x, a minor release may break an app, so a later jadpo doesn't compile a project written for an earlier line. Jadpo won't move the project to another line for you, because the line decides which version of the language the code follows.

What it looks like

app.jadpo:

application {    jadpo: "0.0"}

  |2 |     jadpo: "0.0"  |            ^^^^^ earlier than this jadpo

(human) at the end of the next: line tells your coding agent to stop and ask you which fix you want, because the choice is yours to make: it decides which Jadpo release line the project is written for.

When the installed jadpo tried to fetch the release and couldn't, the reason starts with why, and the next step fits the cause:

• GitHub couldn't be reached: run the command again once this machine can reach github.com.
• GitHub's API refused for its hourly limit: run the command again in an hour.
• No release of the line is published: name a published line in jadpo:.
• There is no cache folder to keep the release in: set XDG_CACHE_HOME to one.
• The download failed its SHA-256 or attestation check: run the command again to fetch it afresh, and if it fails the same way, install the newest jadpo, whose trusted root may be newer.

When jadpo.lock pins an exact release, the error names that release, and the reason says the lock pins it. If no such release is published, the next step is to run jadpo toolchain unpin or pin a published one.

How to fix it

If you set JADPO_TOOLCHAIN=local, run the command without it:

unset JADPO_TOOLCHAINjadpo check

The installed jadpo then runs the release the project names, fetching it once if it doesn't keep it, and the command's own output follows.

If the project should move up to this jadpo's line, bring its code up to that line, then name it: in app.jadpo, the major and minor numbers jadpo --version shows, in place of X.Y:

    jadpo: "X.Y"

This jadpo now checks and runs the project itself.

Related

• Which jadpo runs
• Fetching a release
• When the release can't be run
• Run your own build on every project
• The root