Sometimes yarn outdated misses some packages

[tettoffensive]

Often I'll run yarn outdated to see which dependencies might need to be upgraded. Most of the time it shows a bunch of packages. But I realized recently there are a bunch of packages that are way behind, yet yarn doesn't know they've been upgraded.

For example in my package.json:

"@emotion/css": "^11.1.3",

But the latest version on https://yarnpkg.com/package/@emotion/css is 11.5.0 and on https://www.npmjs.com/package/@emotion/css is 11.9.0

What am I missing? Is there some kind of caching going on?