chore(deps): stop Dependabot re-proposing elysia-rate-limit majors (#362)

elysia-rate-limit 5.x declares `elysia >= 2.0.0` as a peer, but Elysia
has no stable 2.0.0 — the 2.x line is published only under the `next`
(2.0.0-beta.4) and `experimental` (2.0.0-exp.63) dist-tags, while
`latest` is still 1.4.29. `elysia` is already major-ignored here, so
without a matching entry Dependabot re-opens the same unmergeable
elysia-rate-limit 5.x PR every week (#351).

4.6.2 is the newest 4.x and its peer range (`elysia >= 1.0.0`) is
satisfied. Mirrors the @astrojs/cloudflare entry in the docs ecosystem,
which is held back for the same reason: a plugin major that requires a
framework major we have not taken.

Author: agjs

.github/dependabot.yml

@@ -41,6 +41,13 @@ updates:
     ignore:
       - dependency-name: "elysia"
         update-types: ["version-update:semver-major"]
+      # elysia-rate-limit 5.x requires `elysia >= 2.0.0`, but Elysia has no
+      # stable 2.0.0 — the 2.x line exists only under the `next`/`experimental`
+      # dist-tags, and `elysia` itself is major-ignored just above. Stay on
+      # 4.6.2 (peer `elysia >= 1.0.0`) until Elysia 2 ships stable and we do
+      # that upgrade deliberately.
+      - dependency-name: "elysia-rate-limit"
+        update-types: ["version-update:semver-major"]
       - dependency-name: "drizzle-orm"
         update-types: ["version-update:semver-major"]
       - dependency-name: "drizzle-kit"