label-studio-ml-backend
label-studio-ml-backend copied to clipboard
build(deps): bump gunicorn from 22.0.0 to 23.0.0 in /label_studio_ml/examples/segment_anything_model
Bumps gunicorn from 22.0.0 to 23.0.0.
Release notes
Sourced from gunicorn's releases.
23.0.0
Gunicorn 23.0.0 has been released. This version improve HTTP 1.1. support and which improve safety
You're invited to upgrade asap your own installation.
23.0.0 - 2024-08-10
- minor docs fixes (:pr:
3217, :pr:3089, :pr:3167)- worker_class parameter accepts a class (:pr:
3079)- fix deadlock if request terminated during chunked parsing (:pr:
2688)- permit receiving Transfer-Encodings: compress, deflate, gzip (:pr:
3261)- permit Transfer-Encoding headers specifying multiple encodings. note: no parameters, still (:pr:
3261)- sdist generation now explicitly excludes sphinx build folder (:pr:
3257)- decode bytes-typed status (as can be passed by gevent) as utf-8 instead of raising
TypeError(:pr:2336)- raise correct Exception when encounting invalid chunked requests (:pr:
3258)- the SCRIPT_NAME and PATH_INFO headers, when received from allowed forwarders, are no longer restricted for containing an underscore (:pr:
3192)- include IPv6 loopback address
[::1]in default for :ref:forwarded-allow-ipsand :ref:proxy-allow-ips(:pr:3192)** NOTE **
- The SCRIPT_NAME change mitigates a regression that appeared first in the 22.0.0 release
- Review your :ref:
forwarded-allow-ipssetting if you are still not seeing the SCRIPT_NAME transmitted- Review your :ref:
forwarder-headerssetting if you are missing headers after upgrading from a version prior to 22.0.0** Breaking changes **
- refuse requests where the uri field is empty (:pr:
3255)- refuse requests with invalid CR/LR/NUL in heade field values (:pr:
3253)- remove temporary
--tolerate-dangerous-framingswitch from 22.0 (:pr:3260)- If any of the breaking changes affect you, be aware that now refused requests can post a security problem, especially so in setups involving request pipe-lining and/or proxies.
Fix CVE-2024-1135
Commits
411986dfix doc334392eMerge pull request #2559 from laggardkernel/bugfix/reexec-enve75c353Merge pull request #3189 from pajod/patch-py369357b28keep document user in access_log_format setting79fdef0bump to 23.0.03acd9fbMerge pull request #2620 from talkerbox/improve-access-log-format-docs3f56d76Merge pull request #3192 from pajod/patch-allowed-script-name256d474docs: revert duped directiveffa48b5test: default change was intentional52538cadocs: recommend SCRIPT_NAME=/subfolder- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.