Skip to content

0.64.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 16 Oct 20:56
· 82 commits to main since this release
v0.64.0
7cc0c1b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's new

  • Imported Drive documents retain their Google URL and edit time in shared search (cli-core 0.301.0). --source drive:<profile> selects a registered Drive profile; chat document lists can show the imported title after Drive sync links the stored messages.

  • The MCP server loads only when MCP is served (cli-core 0.300.0), so other commands start with about a tenth
    fewer files to load.

Fixed

  • tg setup --app auto no longer tries to create a second app when the account already has one. It read the
    app's keys only from one exact page layout; when my.telegram.org showed the app's page in another shape, it took
    the account for one with no app and asked the site to create another (Telegram allows one per number). Keys are
    now read from the page's text, and an app page whose keys cannot be read stops with "use --app browser". An
    error from the site no longer quotes a whole page — which could hold the app's api_hash — only its title. The
    hint after a failed app step names the command that was run (tg <profile> setup --app browser), and too many
    tries at the site's code is rate_limited.

  • A login with a 2FA password no longer prints mtcute's "unhandled error: ConnectionClosedError" stack. When a
    login succeeds, mtcute replaces its connections on purpose. The old connection then reported itself closed, and with no
    listener mtcute printed that as a red stack trace, with the account id, right after the hidden password prompt.
    tg now listens for these background errors: the expected close shows only with --verbose, and any other appears
    as one line in tg's own words.

  • bin/release restarts itself once when the release brings a newer bin/release: folding the changelog and
    raising the version both fast-forward main, and the shell went on reading the old script from the byte it had
    reached, so the rest of the run was a mix of old and new text. It now starts the new script over with the same
    arguments; a second change during that run stops it with run it again. The restart also works when
    bin/release was started from another folder by a relative path. Only the repository's own release is affected;
    the published package does not change.

Assets 2
Loading