Skip to content
This repository has been archived by the owner on May 14, 2020. It is now read-only.

[Snyk] Upgrade node-telegram-bot-api from 0.30.0 to 0.40.0 #2

Closed

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade node-telegram-bot-api from 0.30.0 to 0.40.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 5 months ago, on 2019-10-17.
Release notes
Package name: node-telegram-bot-api
  • 0.40.0 - 2019-10-17
  • 0.30.0 - 2017-12-21

    Added:

    1. Support Bot API v3.5: (by @GochoMugo)
      • Allow provider_data parameter in TelegramBot#sendInvoice
      • Add method TelegramBot#sendMediaGroup()
    2. Support Bot API v3.4: (by @kamikazechaser)
      • Add methods TelegramBot#editMessageLiveLocation, TelegramBot#stopMessageLiveLocation (#439)
      • Add methods TelegramBot#setChatStickerSet, TelegramBot#deleteChatStickerSet (#440)
    3. Add methods:
    4. Add options to TelegramBot#stopPolling() (by @GochoMugo)
    5. Add metadata argument in message event (and friends e.g. text, audio, etc.) (#409) (by @jlsjonas, @GochoMugo)
    6. Add forward-compatibility i.e. support future additional Telegram options (by @GochoMugo)
    7. Add support for Node.js v9 (by @GochoMugo)
    8. Document TelegramBot.errors, TelegramBot.messageTypes (by @GochoMugo)

    Changed:

    1. Update TelegramBot#answerCallbackQuery() signature (by @GochoMugo)
    2. Improve default error logging of polling_error and webhook_error (#377)
    3. Update dependencies

    Deprecated:

    1. Sending files: (See [usage guide][usage-sending-files]) (by @hufan-akari, @GochoMugo)
      • Error will not be thrown if Buffer is used and file-type could not be detected.
      • Filename will not be set to data.${ext} if Buffer is used
      • Content type will not default to null or undefined

    Fixed:

    1. Fix the offset infinite loop bug (#265, #36) (by @GochoMugo)
    2. Fix game example (#449, #418) (by @MCSH)
from node-telegram-bot-api GitHub release notes
Commit messages
Package name: node-telegram-bot-api
  • 667380f test: skip sendContact
  • 5553cee release: tidy up
  • e66243a [Docs] Update documentation (#753)
  • 1f1e46e test: skip stopMessageLiveLocation
  • 690c26f [Package] Bump to v.0.40.0 (#752)
  • 0613a1b test: temporarily disable pr builds
  • 7feb884 test: update test suite
  • a0aa873 test: Run tests on Node.js v10, v12
  • 0b8ca03 chore/mr: Merge MR #720
  • f1a044e src: Support Bot API v4.2
  • 0b476fe Merge pull request #678 from alexandercerutti/master
  • cf28a17 Added node-telegram-operation-manager to community field
  • 8a51b70 Copyright Updated (#658)
  • d6f5639 Update badges (#667)
  • 47bea20 [Tests] Update
  • 29e0038 Merge pull request #627 from vito2005/patch-1
  • d70442d Merge pull request #613 from mashed-potatoes/master
  • 6e46f48 Merge pull request #671 from kamikazechaser/fix/v4
  • 6a7c088 [v4.0] Add tests and add minor improvement
  • 11a6b22 Merge pull request #636 from sinchang-bot/patch-1
  • 42b31fb Merge pull request #625 from kamikazechaser/api-v4
  • ca7eee8 doc: fix typo
  • e207ef6 one more tutorial for node-telegram-bot-api
  • cca75ec Add documentation

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@dmitriz dmitriz closed this May 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants