chore(deps-dev): update telegramify-markdown requirement from <0.6.0,>=0.5.0 to >=0.5.0,<1.2.0

[dependabot]

Updates the requirements on telegramify-markdown to permit the latest version.

Release notes

Sourced from telegramify-markdown's releases.

v1.1.1

Bug Fixes

• Fix mermaid caption exceeding Telegram length limit — Mermaid live edit URLs are pako-encoded and grow with diagram complexity, easily exceeding Telegram's 1024-code-unit caption limit. The caption now uses a compact text_link entity ("Edit on mermaid.live") instead of a bare URL. (#104, thanks @​Shulyaka for reporting)

0.x Compatibility

• Accept deprecated max_line_length and normalize_whitespace parameters — markdownify(), standardize(), and telegramify() now accept these 0.x parameters without raising TypeError. They are silently ignored with a DeprecationWarning and will be removed in 2.0.

Full Changelog: sudoskys/telegramify-markdown@pypi_1.1.0...pypi_1.1.1

Commits

• 7687e5b chore: bump version to 1.1.1
• 4e4905b fix: use text_link entity for mermaid caption to avoid length overflow
• 7931582 chore: bump version to 1.1.0
• 79bcf0b feat: add render_mermaid and min_file_lines options to telegramify (#103)
• 03205e1 docs: update README for 1.0.0 stable release
• ab182fd Merge pull request #102 from sudoskys/release/1.0.0
• e5776e5 feat: restore 0.x compat API and release 1.0.0
• 80c6140 feat: add entities_to_markdownv2() for reverse conversion (#101)
• 953034d docs: update README for heading level 1-6 support and clean mode config
• 012b62c fix: improve list formatting, task markers, and heading styles (#99)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[JiwaniZakir]

The version ceiling bump in pyproject.toml (line 101) widens the allowed range from <0.6.0 to <1.2.0, which spans several minor and a full major version jump. Since semantic versioning implies breaking changes between major versions, allowing >=1.0.0 without any validation of the v1.x API compatibility is a risk — it's worth checking whether the telegramify-markdown changelog introduces breaking changes in the 1.x series that could affect how Telegram messages are formatted at runtime.

It would also be worth noting why the upper bound stops at <1.2.0 specifically rather than <2.0.0 or just unpinning the major. If 1.2.0 is the latest tested version, a comment or a lock file update confirming that would add confidence. If this range was chosen arbitrarily, tightening it to >=0.5.0,<2.0.0 (trusting semver) or to a specific known-good version like >=0.5.0,<1.3.0 with a note would be more defensible.