install.yanked

The release you asked for has been yanked, so it can't be newly installed.

Area 14, Tooling; not declinable; the next step is usually the human's.

Why Jadpo refuses it

A releaser can yank a release that should no longer be used. Apps that have it keep working, since the code is committed in them, and nothing installs it anew. Jadpo never takes a yanked release by itself, so this comes only when you name one, or when a package has no other.

What it looks like

An app asks for a release its publisher withdrew:

jadpo package add @acme/postcodes --to 2.1.0

(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 release your app runs.

How to fix it

If you named the release, take the newest good one by leaving out --to:

jadpo package add @acme/postcodes

The newest release that isn't yanked or a pre-release is installed instead.

If you have it installed, see whether an advisory touches it and move on:

jadpo package auditjadpo package update postcodes

The app keeps working until you do, and then runs the newer release.

Related

• Yanks, takedowns and advisories