ForgeFlux/nodeinfo-test
2
0
Fork 0
Code Issues 1 Pull requests 7 Projects Releases Packages Wiki Activity

chore(deps): update dependency charset-normalizer to v3.4.1 #36

Open
renovate-bot wants to merge 1 commit from renovate/charset-normalizer-3.x into master
pull from: renovate/charset-normalizer-3.x
merge into: ForgeFlux:master
Conversation 0 Commits 1 Files changed 1 +2 -2
renovate-bot commented 2024-10-09 13:37:16 +05:30
Member
Copy link

This PR contains the following updates:

Package Update Change
charset-normalizer (changelog) minor ==3.3.2 -> ==3.4.1

Release Notes

jawah/charset_normalizer (charset-normalizer)

v3.4.1

Compare Source

Changed
  • Project metadata are now stored using pyproject.toml instead of setup.cfg using setuptools as the build backend.
  • Enforce annotation delayed loading for a simpler and consistent types in the project.
  • Optional mypyc compilation upgraded to version 1.14 for Python >= 3.8
Added
  • pre-commit configuration.
  • noxfile.
Removed
  • build-requirements.txt as per using pyproject.toml native build configuration.
  • bin/integration.py and bin/serve.py in favor of downstream integration test (see noxfile).
  • setup.cfg in favor of pyproject.toml metadata configuration.
  • Unused utils.range_scan function.
Fixed
  • Converting content to Unicode bytes may insert utf_8 instead of preferred utf-8. (#​572)
  • Deprecation warning "'count' is passed as positional argument" when converting to Unicode bytes on Python 3.13+

v3.4.0

Compare Source

Added
  • Argument --no-preemptive in the CLI to prevent the detector to search for hints.
  • Support for Python 3.13 (#​512)
Fixed
  • Relax the TypeError exception thrown when trying to compare a CharsetMatch with anything else than a CharsetMatch.
  • Improved the general reliability of the detector based on user feedbacks. (#​520) (#​509) (#​498) (#​407) (#​537)
  • Declared charset in content (preemptive detection) not changed when converting to utf-8 bytes. (#​381)

Configuration

📅 Schedule: 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 this update again.

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

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [charset-normalizer](https://github.com/jawah/charset_normalizer) ([changelog](https://github.com/jawah/charset_normalizer/blob/master/CHANGELOG.md)) | minor | `==3.3.2` -> `==3.4.1` | --- ### Release Notes <details> <summary>jawah/charset_normalizer (charset-normalizer)</summary> ### [`v3.4.1`](https://github.com/jawah/charset_normalizer/blob/HEAD/CHANGELOG.md#341-2024-12-24) [Compare Source](https://github.com/jawah/charset_normalizer/compare/3.4.0...3.4.1) ##### Changed - Project metadata are now stored using `pyproject.toml` instead of `setup.cfg` using setuptools as the build backend. - Enforce annotation delayed loading for a simpler and consistent types in the project. - Optional mypyc compilation upgraded to version 1.14 for Python >= 3.8 ##### Added - pre-commit configuration. - noxfile. ##### Removed - `build-requirements.txt` as per using `pyproject.toml` native build configuration. - `bin/integration.py` and `bin/serve.py` in favor of downstream integration test (see noxfile). - `setup.cfg` in favor of `pyproject.toml` metadata configuration. - Unused `utils.range_scan` function. ##### Fixed - Converting content to Unicode bytes may insert `utf_8` instead of preferred `utf-8`. ([#&#8203;572](https://github.com/jawah/charset_normalizer/issues/572)) - Deprecation warning "'count' is passed as positional argument" when converting to Unicode bytes on Python 3.13+ ### [`v3.4.0`](https://github.com/jawah/charset_normalizer/blob/HEAD/CHANGELOG.md#340-2024-10-08) [Compare Source](https://github.com/jawah/charset_normalizer/compare/3.3.2...3.4.0) ##### Added - Argument `--no-preemptive` in the CLI to prevent the detector to search for hints. - Support for Python 3.13 ([#&#8203;512](https://github.com/jawah/charset_normalizer/issues/512)) ##### Fixed - Relax the TypeError exception thrown when trying to compare a CharsetMatch with anything else than a CharsetMatch. - Improved the general reliability of the detector based on user feedbacks. ([#&#8203;520](https://github.com/jawah/charset_normalizer/issues/520)) ([#&#8203;509](https://github.com/jawah/charset_normalizer/issues/509)) ([#&#8203;498](https://github.com/jawah/charset_normalizer/issues/498)) ([#&#8203;407](https://github.com/jawah/charset_normalizer/issues/407)) ([#&#8203;537](https://github.com/jawah/charset_normalizer/issues/537)) - Declared charset in content (preemptive detection) not changed when converting to utf-8 bytes. ([#&#8203;381](https://github.com/jawah/charset_normalizer/issues/381)) </details> --- ### Configuration 📅 **Schedule**: 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 this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOC4xMTQuMCIsInVwZGF0ZWRJblZlciI6IjM5Ljg2LjAiLCJ0YXJnZXRCcmFuY2giOiJtYXN0ZXIiLCJsYWJlbHMiOlsicmVub3ZhdGUtYm90Il19-->
renovate-bot added the
renovate-bot
 label 2024-10-09 13:37:16 +05:30
renovate-bot added 1 commit 2024-10-09 13:37:17 +05:30
chore(deps): update dependency charset-normalizer to v3.4.0
All checks were successful
ci/woodpecker/pr/woodpecker Pipeline was successful
Details
561588314f
renovate-bot changed title from chore(deps): update dependency charset-normalizer to v3.4.0 to chore(deps): update dependency charset-normalizer to v3.4.1 2024-12-30 05:19:57 +05:30
renovate-bot force-pushed renovate/charset-normalizer-3.x from 561588314f to fb5945d89c 2024-12-30 05:19:58 +05:30 Compare
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/charset-normalizer-3.x:renovate/charset-normalizer-3.x
git checkout renovate/charset-normalizer-3.x

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git checkout master
git merge --no-ff renovate/charset-normalizer-3.x
git checkout renovate/charset-normalizer-3.x
git rebase master
git checkout master
git merge --ff-only renovate/charset-normalizer-3.x
git checkout renovate/charset-normalizer-3.x
git rebase master
git checkout master
git merge --no-ff renovate/charset-normalizer-3.x
git checkout master
git merge --squash renovate/charset-normalizer-3.x
git checkout master
git merge --ff-only renovate/charset-normalizer-3.x
git checkout master
git merge renovate/charset-normalizer-3.x
git push origin master
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
  
renovate-bot

   
renovate-security

   
security
No labels
renovate-bot
renovate-security
security
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: ForgeFlux/nodeinfo-test#36
No description provided.
Delete branch "renovate/charset-normalizer-3.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?