[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
charset-normalizer (changelog)	==3.4.7 → ==3.5.2
charset-normalizer (changelog)	==2.1.1 → ==3.5.2

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

Release Notes

jawah/charset_normalizer (charset-normalizer)

v3.5.2

Compare Source

Changed

• Raised the Cython upper bound to <3.4 for native builds. The bound remains <3.3 for
  abi3 builds to preserve compatibility with the Python 3.7 Limited API.

Fixed

• Valid UTF-8 Chinese JSON incorrectly detected as PTCP154 due to excessive noise penalties
  for uncommon CJK characters. (#​796)
• Supported encodings without aliases failing name resolution or being ignored in charset
  declarations. (#​800)

v3.5.1

Compare Source

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.

v3.5.0

Compare Source

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).

v3.4.9

Compare Source

Fixed

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

v3.4.8

Compare Source

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)

Changed

• No longer holding a global cache for our noise / coherence measurements. Relax RSS memory usage.
• Micro-optimizations in our noise / coherence measurements.
• No longer using regex search by default for our preemptive charset mark algorithm.
• Raised upperbound of setuptools to v83.
• Raised upperbound of mypy(c) to v2.1.

Removed

• Redundant UTF7 BOM marker (#​730)

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Auto-approved: Run Pgskipper Pipeline passed and all commits are verified and authored by renovate[bot].

[github-actions]

Auto-approved: Run Pgskipper Pipeline passed and all commits are verified and authored by renovate[bot].

[github-actions]

Auto-approved: Run Pgskipper Pipeline passed and all commits are verified and authored by renovate[bot].

[NetcrackerCLPLCI]

🤖 CI-Autofix — could not fix this automatically

Classification: behavioral
Reason: infra

What broke

robot-framework-failed

[COMPARE] deployment dbaas-postgres-adapter dbaas-postgres-adapter ghcr.io/netcracker/pgskipper-docker-dbaas-adapter:main: Expected tag=main, Actual tag=main
| PASS |
------------------------------------------------------------------------------
Tests.Image Tests.Image Tests                                         | PASS |
1 test, 1 passed, 0 failed
==============================================================================
Tests.Image Tests                                                     | PASS |
1 test, 1 passed, 0 failed
==============================================================================
Tests                                                                 | FAIL |
47 tests, 42 passed, 4 failed, 1 skipped
==============================================================================
Output:  /opt/robot/output/output.xml
Log:     /opt/robot/output/log.html
Report:  /opt/robot/output/report.html
##[error] ❌ Tests failed
##[end-action id=__self_5.__run_5;outcome=success;conclusion=success;duration_ms=175]
##[start-action display=Check job status;id=__self_5.__run_6]
##[group]Run # ▶️ Check deploy status
# ▶️ Check deploy status

The PR only bumps charset-normalizer (a transitive dependency of requests) in services/backup-daemon/docker/requirements.txt; no code in the repo imports or calls charset_normalizer/chardet directly, and a dry-run pip install of the updated requirements resolves cleanly with no conflicts. The failing Robot Framework 'Check Granular Api' E2E suite requires a live Kubernetes/Patroni/S3 deployment that cannot be run in this sandbox, and the job log shows the identical suite producing different failure counts (0, 8, 0 of 12 tests) across the three parallel pg16/17/18 jobs for the same commit — a signature of pre-existing environment/timing flakiness (tests mint namespace/backup ids at minute granularity) rather than a deterministic regression caused by this dependency bump. No in-scope code change was found that would address this, so no fix was applied.

No commit was pushed. Suggested next step: a human needs to make the fix

---

Attempt 1 of 2 · model: global.anthropic.claude-sonnet-5