is this repo suddenly missing from the npm registry?

[krisdock]

we're seeing 404 errors across multiple repo workflows

[aweber1]

Same

[dlenroc]

Confirmed — I’m also unable to view or download it. I’ve reached out to NPM support, as older versions exist but aren’t accessible.

In the meantime, I republished the latest version as 1.9.4: 79288ad.

If it doesn’t download automatically, use an NPM override to enforce this version:

"overrides": {
  "@dlenroc/testrail": "^1.9.4"
}

[lfgcampos]

hey @dlenroc, any explanation to what happened here? 😅

[dlenroc]

hey @dlenroc, any explanation to what happened here? 😅

Some bad-faith actors exploited the DMCA process to shut down my repositories and npm packages. A counter-notice was filed immediately, but due to a sync issue between GitHub and npm, some packages were removed from npm while remaining on GitHub.

A short interim version was published (this issue), but it was later shut down again, along with all repositories at that time.

After further communication with GitHub and npm support, the repositories were reinstated (today). However, restoring older npm package versions is not currently possible due to technical issues on the npm side, and there is no ETA for when they will be available.

In the meantime, to ensure continued use—including for myself—I will republish the latest versions as a patch release 1.9.5.

[lfgcampos]

Thanks for the timely update @dlenroc!