Skip to content

Commit

Permalink
Bump version to v13.8.1
Browse files Browse the repository at this point in the history
  • Loading branch information
@Bibo-Joshi
Bibo-Joshi committed Nov 8, 2021
1 parent 8b3ea5c commit c53dc7d
Show file tree
Hide file tree
Showing 3 changed files with 15 additions and 3 deletions.
12 changes: 12 additions & 0 deletions CHANGES.rst
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,18 @@
Changelog
=========

Version 13.8.1
==============
*Released 2021-11-08*

This is the technical changelog for version 13.8.1. More elaborate release notes can be found in the news channel `@pythontelegrambotchannel <https://t.me/pythontelegrambotchannel>`_.

**Doc fixes:**

- Add ``ChatJoinRequest(Handler)`` to Docs (`#2771`_)

.. _`#2771`: https://github.com/python-telegram-bot/python-telegram-bot/pull/2771

Version 13.8
============
*Released 2021-11-08*
Expand Down
4 changes: 2 additions & 2 deletions docs/source/conf.py
View file
Original file line number Diff line number Diff line change
Expand Up @@ -60,9 +60,9 @@
# built documents.
#
# The short X.Y version.
version = '13.8' # telegram.__version__[:3]
version = '13.8.1' # telegram.__version__[:3]
# The full version, including alpha/beta/rc tags.
release = '13.8' # telegram.__version__
release = '13.8.1' # telegram.__version__

# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.
Expand Down
2 changes: 1 addition & 1 deletion telegram/version.py
View file
Original file line number Diff line number Diff line change
Expand Up @@ -20,5 +20,5 @@

from telegram import constants

__version__ = '13.8'
__version__ = '13.8.1'
bot_api_version = constants.BOT_API_VERSION # pylint: disable=C0103

1 comment on commit c53dc7d

@xmatthias
Copy link

@xmatthias xmatthias commented on c53dc7d Nov 11, 2021 •
edited

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rest assured that the organizational skills of this libraries developer group are quite sufficient to keep track of the changes that we want to include in a release.

@Bibo-Joshi
May i ask why you did not stick to the comment you made in #2757 (comment) (highlight quoted above).
I was assuming and trusting that what you claim is true ... but it seems like you "simply forgot" - as i rightly pointed out in that Pull request (which is clear, and was obvious, as an open source maintainer will not remember random issues right before creating a release).

As you did a release, simply accepting the PR (or suggesting improvements if you thought it should've been done differently) would've upgraded the Dependency without any problems...

Please sign in to comment.