deps: batch dependabot #304-#308 (+ grammy 1.46.0, sharp security patch) - #312
Merged
Conversation
… 1.46.0 Merging the five branches individually conflicts on the lockfile, so this takes them as one package.json edit plus a single npm install. #308 bumps @grammyjs/types 3.27.3 -> 5.0.0 on its own, which is the known trap: grammy bundles its own copy, and a newer top-level one breaks typecheck at src/bot/context.ts. grammy 1.46.0 bundles exactly 5.0.0, so taking both together keeps the two aligned and defuses it — verified as a single installed copy at 5.0.0 with no nested duplicate. Also bumps sharp 0.35.3 -> 0.35.4, a patch clearing a high-severity libheif advisory (GHSA-rgj7-g3m4-5g8c) on a direct dep used by nft-handler. npm audit goes 1 high -> 0.
This was referenced Sep 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Takes all five open Dependabot PRs as one commit. Merging the branches individually conflicts on the lockfile, so this is a single
package.jsonedit plus onenpm install.src/frontend, kept in lockstep)#308 needed a companion bump
Taken alone, #308 is the documented trap:
grammybundles its own@grammyjs/types, and forcing a newer one at top level breaks typecheck atsrc/bot/context.ts(UserFromGetMe/supports_join_request_queriesmismatch). Dependabot only ever proposes the types half, which is why this PR has sat open.grammy1.46.0 bundles exactly@grammyjs/types5.0.0, so taking both together keeps them aligned rather than walking into the mismatch. Verified there's a single installed copy at 5.0.0 with no nested duplicate undernode_modules/grammy/. This also carries grammy 1.43.0 → 1.46.0.Unrelated security patch included
sharp0.35.3 → 0.35.4 — a patch clearing a high-severity libheif advisory (GHSA-rgj7-g3m4-5g8c) on a direct dep used bynft-handler.ts.npm auditgoes 1 high → 0.Verification
npm run lint,npm run typecheckclean — typecheck being green is the specific thing the trap would have brokennpm run test:backend625/625npm run build:allclean (backend emit + landing + frontend)npm run smoke:apiall steps greennpm audit0 vulnerabilitiesCaveat worth stating: the smoke test runs in STAGING mode, which skips Telegram entirely, so nothing here exercises grammy 1.46.0 at runtime — a three-minor bump of the bot framework is the one change in this batch that automated gates can't cover. Staging deploy (@cubeworldsbot) is the real check; that's the next step after this merges.