Is there any mechanism to bypass the latest canary version check when running next lint?

I'm reworking a bunch of code (in this case, unrelated to the Next.js code, rather focused on database migrations and schema updates) and want to run next lint as a convenient way to check if it seems plausible.
However, I last built this code for 15.0.4-canary.49, which was at the time the latest, but is now definitely not.

I'm a bit confused about how the (local) linter 'knows' that this is old, given the plugin is also for v15.0.4, but I tried updating to canary.52 (which I think was the last 15.0.4 version before it released) in case that helped - it did not.

I can probably run the build with linting disabled to check TypeScript etc, but the linting is normally quite useful, and it'd be nice to run it here. I could also remove the 'experimental.ppr' flag (especially because soon I'll be removing it in favour of cacheComponents), but then various other things might change/break that I'm not considering here...