Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
Tried to install the day a release went out and got this, which I cannot make sense of:
No matching version found for @sdods/agents@0.2.2 with a date before 2026-04-21T00:00:00.000ZThe version exists — I can see it on npm and npm i -g @sdods/cli works fine on the same machine. So why does brew think it does not?
Accepted answer
The formula is correct and the package exists. It is too new.
Homebrew builds node formulae with std_npm_args, which passes --min-release-age. npm then refuses any dependency published inside that window, and the message it prints is the one you pasted — it reads like "this version does not exist" but it means "this version is younger than the floor I was given".
There is nothing to fix on your side. Wait for the packages to age past the window and the same command installs. If you need it today, npm has no such floor:
npm install -g @sdods/cliThis is also why the formula is never pushed the same day the packages are published — it would be correct and uninstallable, which is the worst combination.
Confirming from the other side of it: I hit the same message on Tuesday, changed nothing at all, and it installed on Thursday. Do not go editing the formula locally, you will only give yourself a second problem.
If you use the install script instead of brew you never see this either — it fetches the published packages directly and has no release-age policy of its own.
curl -fsSL https://sdods.com/install.sh | shWrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.