Repository navigation
Bump native tls-client library to v1.18.1 - #169
Open
felipeadeildo wants to merge 2 commits into
Open
felipeadeildo wants to merge 2 commits into
felipeadeildo wants to merge 2 commits into
Conversation
Adds the chrome_154, chrome_154_PSK and safari_27_2 identifiers, the only profiles upstream added since v1.16.0. SHA256SUMS still pins v1.16.0: the v1.18.1 release has no binaries yet.
The v1.18.1 release now has its binaries, built with the chrome_154, chrome_154_PSK and safari_27_2 profiles.
felipeadeildo
marked this pull request as ready for review
November 13, 2026 14:20
This branch has not been deployed
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.
Bumps the bundled bogdanfinn/tls-client from v1.16.0 to v1.18.1.
Changes
scripts/fetch_library.py:VERSION = "1.18.1".tls_client/dependencies/SHA256SUMS: pins the v1.18.1 libraries.tls_client/settings.py: addschrome_154,chrome_154_PSKandsafari_27_2, so the list matches upstream'sMappedTLSClientsexactly.What Python users get
chrome_150, the upstream default, now sends the trust_anchors extension like real Chrome 150.The breaking changes need nothing from the wrapper:
sessionId.Accept-Encoding.Testing
I ran the tests with the official
tls-client-linux-ubuntu-amd64.sofrom the v1.18.1 release. It knows every identifier insettings.py, including the three new ones.chrome_150gives JA4t13d1517h2_8daaf6152771_cb7bf5808d99, the value the release notes list for real Chrome 150.Follow-up idea
A daily workflow could watch bogdanfinn's releases and open a bump PR like this one, so the bundled library doesn't fall behind again. I can send it separately if you want it.