chore(deps): bump charset-normalizer from 3.4.7 to 3.5.1

[dependabot]

Bumps charset-normalizer from 3.4.7 to 3.5.1.

Release notes

Sourced from charset-normalizer's releases.

Version 3.5.1

3.5.1 (2026-08-15)

Changed

• Raised upper bound of setuptools to v84 (#794)
• Cache performance access optimization for our CharInfo struct (prebuilt only).

Fixed

• No longer decoding large content when the noise detector output give a high entropy. Only impacted large content input >1M bytes.

Version 3.5.0

3.5.0 (2026-08-12)

Added

• Explicit support for Python 3.15

Fixed

• Comparing a CharsetMatch to a non-alias encoding strings (#773)
• Return 0.0 CharsetMatch.multi_byte_usage for empty payloads instead of crashing (#774)
• A file with both a charset declaration and BOM/SIG did not verify first the BOM/SIG charset.
• iso2022* cases misdetected due to a flaw in our multibyte chunking logic.

Changed

• Replaced the optional mypyc build with Cython extensions while retaining the pure Python fallback. The previous engine (mypyc) started to hit rough limit around the optimization of our noise/coherence detector while Cython allows us to steer the engine toward the right generated optimized sources. This change SHOULD not impact bundler (e.g. Pyinstaller) as the module are immediately discoverable (i.e. not hidden import like mypyc did). Moreover, a long wished distribution is the abi3 wheels, this will allow us to no longer rush each year when a new Python interpreter is released. We still distribute the interpreter specific wheels for faster performance.
• Applied micro-optimization on several utils.
• CharsetMatches no longer sort on each match insertion.

Misc

• Removed an old performance optimization attempt in apy.py (success_fast_tracked+payload_result_cache).

Version 3.4.9

3.4.9 (2026-07-07)

Fixed

• Regression in our fallback path leading to a decode error. (#771) We've yanked 3.4.8 as a result of that bug.

Version 3.4.8

3.4.8 (2026-07-06)

Fixed

... (truncated)

Changelog

Sourced from charset-normalizer's changelog.

3.5.1 (2026-08-15)

Changed

• Raised upper bound of setuptools to v84 (#794)
• Cache performance access optimization for our CharInfo struct (prebuilt only).

Fixed

• No longer decoding large content when the noise detector output give a high entropy. Only impacted large content input >1M bytes.

3.5.0 (2026-08-12)

Added

• Explicit support for Python 3.15

Fixed

• Comparing a CharsetMatch to a non-alias encoding strings (#773)
• Return 0.0 CharsetMatch.multi_byte_usage for empty payloads instead of crashing (#774)
• A file with both a charset declaration and BOM/SIG did not verify first the BOM/SIG charset.
• iso2022* cases misdetected due to a flaw in our multibyte chunking logic.

Changed

• Replaced the optional mypyc build with Cython extensions while retaining the pure Python fallback. The previous engine (mypyc) started to hit rough limit around the optimization of our noise/coherence detector while Cython allows us to steer the engine toward the right generated optimized sources. This change SHOULD not impact bundler (e.g. Pyinstaller) as the module are immediately discoverable (i.e. not hidden import like mypyc did). Moreover, a long wished distribution is the abi3 wheels, this will allow us to no longer rush each year when a new Python interpreter is released. We still distribute the interpreter specific wheels for faster performance.
• Applied micro-optimization on several utils.
• CharsetMatches no longer sort on each match insertion.

Misc

• Removed an old performance optimization attempt in apy.py (success_fast_tracked+payload_result_cache).

3.4.9 (2026-07-07)

Fixed

• Regression in our fallback path leading to a decode error. (#771) We've yanked 3.4.8 as a result of that bug.

3.4.8 (2026-07-06)

Fixed

• Wall import time due to cascade codec imports for our multibyte first sort of iana supported codecs (#742)
• Unnecessary json import at runtime (#753)
• Inverse capitalization not seen by noise detector (#731)

... (truncated)

Commits

• e239bdc Merge pull request #795 from jawah/release-3.5.1
• 648ad77 docs: update faq
• fab2749 docs: write changelog for 3.5.1
• 7d32774 chore: bump version to 3.5.1
• 9a69f60 docs: update data/info
• 5dcc6dd perf: charinfo cache access optimization in cython
• ea3b447 fix: do not validate-decode large payload when md says it's noise
• a05917f chore: allow setuptools 84 builds (#794)
• 3325d87 Merge pull request #792 from jawah/update-cibuildwheel-action
• 77203b1 chore: reformat noxfile.py
• Additional commits viewable in compare view

---

[seonghobae]

Exact-current-head review request for e124982b2561e6360681045519d121debbf7bf81 against protected main@eb0ee5c68c9e807644a920c1a5fb4caa1cf2fe97. Current checks are terminal-success and the dependency update (charset-normalizer) is mechanically clean/mergeable. Review this exact head only; do not self-approve or bypass protection.

[seonghobae]

Rebased onto current main9e9f59f3; preserved the current lockfile state plus the charset-normalizer update; exact head 999f1062; diff check passed. Project #1 is In Progress.

[seonghobae]

Current-head rebase published at bf2935966e6f751211a7c8d1fc1f038b6e928968; base is now current main@bbedc1a51ec1a2421f129955c629b3cd0507a4ec. This is a lock-only Dependabot charset-normalizer 3.5.0 update; diff check passes and no implementation change was needed. Protected checks are re-queued; no bypass or self-approval used.

[seonghobae]

Rebased Dependabot update onto current main@c47bee59. Exact head: 03748a0. Current diff was checked for path integrity; required workflow YAML updates were actionlint-validated where applicable, and hash-lock changes retain explicit package/file digests.

[seonghobae]

@OpenCode Please review exact current head 03748a0 against base main@c47bee591c3d95bd305f2130833ed3a4780d2d1d.

[seonghobae]

Rebased Dependabot update onto current main@c47bee59. Exact head: 03748a0. Current diff was checked for path integrity and explicit hash-lock integrity.

[seonghobae]

@OpenCode Please review exact current head 03748a0 against base main@c47bee591c3d95bd305f2130833ed3a4780d2d1d.

[seonghobae]

@opencode-agent review exact current head 97ffca37a169e41c15da8976fcb3484a3ee526ff against protected base 2cce96f8671bfde7e354effef931c14a5928c23b. Rebased this dependency-only hash-lock update onto current main; diff is limited to requirements hash evidence and passes diff --check. Treat predecessor reviews/checks as historical and do not approve from queued or status-only evidence.

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[seonghobae]

@opencode-agent Please review exact current HEAD e7bb8d0c39ff82e289d25d16bc68a4431e2b1978 only. The branch is current with protected main; report actionable findings or approve only this exact commit.

[dependabot]

A newer version of charset-normalizer exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

[opencode-agent]

Pull request overview

OpenCode reviewed the current-head evidence but found unresolved reviewer or review-agent threads before approval.

Findings

1. HIGH .github/workflows/opencode-review.yml:1 - Unresolved reviewer thread blocks automated approval

• Problem: OpenCode reached an APPROVE control result, but the approval step found unresolved, non-outdated human or review-agent thread evidence on the current pull request.
• Root cause: Reviewer and review-agent feedback can arrive after bounded model evidence is prepared, so the approval step must re-query GitHub immediately before publishing an approval.
• Fix: Address or resolve the listed reviewer thread(s), then re-run OpenCode on the current head.
• Regression test: Keep the approval gate querying reviewThreads(first: 100) after model output and before create_pull_review APPROVE, including bot review agents other than OpenCode itself.

Review thread evidence

Latest unresolved reviewer thread evidence

requirements-strix-ci-hashes.txt line 266

• Latest reviewer comment: @devin-ai-integration at 2026-08-21T19:39:05Z

• Comment URL: #1104 (comment)

• Comment excerpt: <!-- devin-review-comment {"id": "ANALYSIS_pr-review-job-720b653985814cd8b0736e40ca5f5213_0001", "file_path": "requirements-strix-ci-hashes.txt", "start_line": 266, "end_line": 266, "side": "RIGHT", "kind": "analysis"} --> / 📝 Info: Hash sets match across both lockfiles / The 'charset-normalizer==3.5.1' hash block is byte-identical (172 hashes) in requirements-pip-audit-ci-hashes.txt (Python 3.12 compile)

• Result: REQUEST_CHANGES

• Reason: unresolved reviewer or review-agent thread(s) were present before approval.

• Head SHA: d90c8320bcce63269f1ab6368f1073841c157363

• Workflow run: 33114600276

• Workflow attempt: 1

Changed-File Evidence Map

flowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Changed file (2 files)"]
S1 --> I1["repository behavior"]
I1 --> R1["Review risk: Changed file (2 files)"]
R1 --> V1["required checks"]

Loading

[opencode-agent]

OpenCode Review Overview

• Head SHA: d90c8320bcce63269f1ab6368f1073841c157363
• Workflow run: 33114600276
• Workflow attempt: 1
• Gate result: REQUEST_CHANGES (approval step)

Pull request overview

OpenCode reviewed the current-head evidence but found unresolved reviewer or review-agent threads before approval.

Findings

1. HIGH .github/workflows/opencode-review.yml:1 - Unresolved reviewer thread blocks automated approval

• Problem: OpenCode reached an APPROVE control result, but the approval step found unresolved, non-outdated human or review-agent thread evidence on the current pull request.
• Root cause: Reviewer and review-agent feedback can arrive after bounded model evidence is prepared, so the approval step must re-query GitHub immediately before publishing an approval.
• Fix: Address or resolve the listed reviewer thread(s), then re-run OpenCode on the current head.
• Regression test: Keep the approval gate querying reviewThreads(first: 100) after model output and before create_pull_review APPROVE, including bot review agents other than OpenCode itself.

Review thread evidence

Latest unresolved reviewer thread evidence

requirements-strix-ci-hashes.txt line 266

• Latest reviewer comment: @devin-ai-integration at 2026-08-21T19:39:05Z

• Comment URL: chore(deps): bump charset-normalizer from 3.4.7 to 3.5.1 #1104 (comment)

• Comment excerpt: <!-- devin-review-comment {"id": "ANALYSIS_pr-review-job-720b653985814cd8b0736e40ca5f5213_0001", "file_path": "requirements-strix-ci-hashes.txt", "start_line": 266, "end_line": 266, "side": "RIGHT", "kind": "analysis"} --> / 📝 Info: Hash sets match across both lockfiles / The 'charset-normalizer==3.5.1' hash block is byte-identical (172 hashes) in requirements-pip-audit-ci-hashes.txt (Python 3.12 compile)

• Result: REQUEST_CHANGES

• Reason: unresolved reviewer or review-agent thread(s) were present before approval.

• Head SHA: d90c8320bcce63269f1ab6368f1073841c157363

• Workflow run: 33114600276

• Workflow attempt: 1

Changed-File Evidence Map

flowchart LR
PR["PR changed files"] --> Evidence["OpenCode bounded evidence"]
Evidence --> S1["Changed file (2 files)"]
S1 --> I1["repository behavior"]
I1 --> R1["Review risk: Changed file (2 files)"]
R1 --> V1["required checks"]

Loading