Repository navigation
chore: update dependencies and verify Bot API 10.3 sync - #21
Merged
Merged
Conversation
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
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.
Summary
@typescript/nativealias, alongside the@typescript/typescript6compatibility API required by typescript-eslint. Document the setup in README.Telegram Bot API sync
The official documentation's latest release is still Bot API 10.3 (August 24, 2026). Re-fetched 185 methods and 399 types through
pnpm gen:fetch; the upstream snapshot matches the committed spec exactly.pnpm gen:checkreports Nothing to review, and regenerated modules are unchanged. No artificial version bump or manual snapshot/generated-module edits are included.Validation
Passed locally on Node 24.19.0:
pnpm install --frozen-lockfilepnpm lintpnpm typecheckpnpm buildpnpm gen:fetch,pnpm gen:check, andpnpm gen:buildgit diff --exit-code -- src/ spec/(upstream and generated output unchanged)pnpm peers check(no issues)pnpm audit(no known vulnerabilities)pnpm outdated(no outdated direct dependencies)git diff --checkAlso passed
pnpm typecheck,pnpm lint,pnpm gen:check, andpnpm gen:buildunder Node 22.18.0, preserving the existing minimum supported Node version.Release/publishing workflows were not executed. No package or tag is published, and this PR is left unmerged. no-mistakes was skipped as requested.