#npm error notarget No matching version found for @aws-sdk/token-providers@3.1036.0.

1 messages · Page 1 of 1 (latest)

devout mulch
#

I'm getting this error when i try to update from 4.15 to 4.22

left riverBOT
mellow veldtBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

left riverBOT
faint zenithBOT
#

This looks like a registry sync issue, not a bad OpenClaw version.

I checked the public npm registry, and @aws-sdk/token-providers@3.1036.0 does exist now, but it was published very recently. If you're using a mirror, private registry, or cached npm metadata, it may not have propagated yet.

Can you paste these?

openclaw --version
npm config get registry
npm view @aws-sdk/token-providers@3.1036.0 version

If that last command fails, that's the problem.

What I'd try next:

  1. wait 10 to 30 min and retry
devout mulch
faint zenithBOT
#

Nice, that narrows it down a lot.

Since:

  • your registry is the public npm registry
  • npm view @aws-sdk/token-providers@3.1036.0 works
  • I can install openclaw@2026.4.22 cleanly on my side

this looks like stale npm cache / metadata locally, not a broken OpenClaw release.

I'd try this next:

npm cache clean --force
npm install -g openclaw@2026.4.22 --prefer-online
#

Then:

openclaw doctor
openclaw gateway restart

If it still fails, paste these too:

node -v
npm -v
npm install -g openclaw@2026.4.22 --prefer-online

Preferred update docs:

devout mulch
#

it works now, thank you !

faint zenithBOT
#

Glad it’s working now 🎉

If this fixed it, please right-click the solution message → Apps → ✅ Mark Solution so Answer Overflow can index it for the next person.

Sounds like it was just stale npm metadata/cache catching up.