Update dependency @cordis/common to v1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@cordis/common	^0.2.3 → ^1.0.0

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Release Notes

cordis-lib/cordis (@​cordis/common)

v1.2.0

Compare Source

Bug fixes

• fix(WebsocketConnection): no longer hardcode gateway version (#​92)
• fix(DiscordFetch): add highWaterMark option (#​93) - this is a bug fix as before, due to internal request cloning requests to Discord that returned large payloads would cause promises to never resolve
• fix(MemoryMutex): properly update the remaining property - this is a critical fix, as before it would cause lots of rate limits
• fix(Bucket): implement a TLL system for Bucket instances - this is also an important fix at scale, resolving a memory leak
• fix(Bucket): #makeRoute now deals with /channels/:id correctly
• fix(Bucket): group all invite routes into one bucket

v1.0.1

Compare Source

Fixes

• fix(GatewayService): parse for env once more (#​90)
• fix(rest): move discord-api-types into runtime deps (#​91)

v1.0.0

Compare Source

Hiya! Cordis is finally stable. Lots of breaking changes! Officially everything before this version has been deprecated.

Repo & QOL

• ci: add deploy workflow (#​77)
• chore: polish/cleanup (#​76, #​86) - typescript, eslint and other dependency bumps
• chore: automatic changelog generation (#​82)

General refactoring

• chore: polish rest (#​73) - this was a rewrite - breaking
• refactor: remove DI and the pub sub client from GW service (#​84) - breaking
• refactor(Brokers): change confusing client/server naming to publisher/subscriber (#​87) - breaking
• chore: remove relics of the past (#​85) - breaking - this PR removed a lot of stuff
• refactor(WebsocketShard): gateway events (#​88) - breaking

v0.3.0

Compare Source

Hello! Been a while. 0.2 releases turned out to work much better than I thought they would. Cordis has seen quite the volume of use with some of the stuff I've been working on lately and it's just been going super well.

However, with that I managed to find a bunch of issues with rest rate limit handling - and oh lord. The codebase of that thing was a headache. This release is breaking because I have more or less entirely rewrote it.

Here's a list of changes:

• [BREAKING] refactor(Rest#response): The response event was re-done. It now emits once the I/O call is done and gives you a clone of the response.
• [BREAKING] refactor(Mutex#claim): no longer takes in a signal parameter, meaning you cannot cancel a request at this stage anymore - I'm fairly uncertain if this change really is desireable and it may see itself being reverted, but with a different approach. It was really only removed due to some of the problems it was causing
• fix(HTTPError): no longer call Error.captureStackTrace(this); in the constructor - seems like this was causing some trouble, may make the stack traces work better now. Uncertain, but I'll continue bashing down on that problem over the next few patch releases
• fix(Rest/Bucket): error handling - This should've been done ages ago, frankly. A lot of edge cases are now properly covered and recursion is no longer used for retries.
• feat(DiscordFetchOptions#implicitAbortBehavior): tells the library if it should internally set a timeout for the actual I/O being done (fetch) - defaults to false if you pass in your own controller
• feat(DiscordFetchOptions#retryAfterRatelimit): allows you to make 429 status codes just throw instead of wait & retry, defaults to Rest#retryAfterRatelimit.
• feat(Rest#retryAfterRatelimit): default for the above

It's really not that bad. Unless you implemented your own mutex/did whacky stuff with the response event you don't even have to touch your code.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Scope: all 3 workspace projects
Progress: resolved 0, reused 1, downloaded 0, added 0
 WARN  GET https://registry.npmjs.org/@gaius-bot/readdir/-/readdir-1.0.0.tgz error (ERR_PNPM_FETCH_404). Will retry in 10 seconds. 2 retries left.
services/handler                         |  WARN  deprecated @cordis/common@1.2.0
Progress: resolved 36, reused 35, downloaded 1, added 0
 WARN  GET https://registry.npmjs.org/@gaius-bot/readdir/-/readdir-1.0.0.tgz error (ERR_PNPM_FETCH_404). Will retry in 1 minute. 1 retries left.
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/@gaius-bot/readdir/-/readdir-1.0.0.tgz: Not Found - 404

No authorization header was set for the request.