casper/bsky_handle_provider
1
0
Fork 0
Code Issues 1 Pull requests 10 Projects Releases Packages Wiki Activity Actions

Update dependency httparty to "~> 0.24.0" #52

Open
renovate wants to merge 1 commit from renovate/httparty-0.x into main
pull from: renovate/httparty-0.x
merge into: casper:main
Conversation 0 Commits 1 Files changed 2 +3 -3
renovate commented 2025-12-28 22:01:49 +00:00
Collaborator
Copy link

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
httparty (changelog) "~> 0.23.1" → "~> 0.24.0" age adoption passing confidence

Release Notes

jnunemaker/httparty (httparty)

v0.24.3

Compare Source

Full Changelog: https://github.com/jnunemaker/httparty/compare/v0.24.2...v0.24.3

Bug Fixes

  • Support the json gem 3.x, which removed the quirks_mode parser option. (#​846)
  • Fix the MultiXml deprecation warning with multi_xml 0.9+. (#​838, thanks @​robzolkos)
  • A UTF-8 byte order mark (BOM) is now stripped from responses that don't declare a charset. Before, a BOM-prefixed JSON response without a charset raised JSON::ParserError. (#​852)
  • A response body that is only a BOM, or a BOM followed by whitespace, now parses to nil like any other blank body, instead of raising or returning the whitespace. (#​851, thanks @​januththedev)
  • parsed_response and response.body are separate strings for UTF-8 text responses, as in 0.24.2. (#​854)

Performance

  • raise_on with a Range (e.g. 500..599) checks the range directly instead of building a regex for every code in it. (#​843, thanks @​MaxLap)
  • Parsing allocates fewer objects per response. (#​854)

Behavior Changes

For text/plain, text/html and text/csv responses without a charset, a leading BOM is now removed from parsed_response, matching what already happened when charset=utf-8 was set. If you worked around the BOM by matching it (for example a CSV header of "\xEF\xBB\xBFid"), that match will now be "id". Workarounds like delete_prefix("") keep working.

These are unchanged: response.body and to_s (raw bytes), application/octet-stream and other formats HTTParty doesn't parse, and bodies declared in other charsets such as ISO-8859-1 or UTF-16.

Other

v0.24.2

Compare Source

Full Changelog: https://github.com/jnunemaker/httparty/compare/v0.24.1...v0.24.2

Bug Fixes

  • Streaming uploads are now opt-in - The streaming multipart upload feature introduced in 0.24.0 caused compatibility issues with some servers (returning 400 errors). Streaming is now disabled by default to preserve backwards compatibility. Enable it explicitly with stream_body: true for memory-efficient large file uploads. (#​832)

Example


# Default behavior (buffered, compatible with all servers)
HTTParty.post('http://example.com/upload', body: { file: File.open('large.zip') })

# Opt-in to streaming for large files (reduced memory usage)
HTTParty.post('http://example.com/upload', body: { file: File.open('large.zip') }, stream_body: true)

v0.24.1

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/jnunemaker/httparty/compare/v0.24.0...v0.24.1

v0.24.0

Compare Source

What's Changed

Full Changelog: https://github.com/jnunemaker/httparty/compare/v0.23.2...v0.24.0

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

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

This PR has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Adoption](https://docs.renovatebot.com/merge-confidence/) | [Passing](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---|---|---| | [httparty](https://github.com/jnunemaker/httparty) ([changelog](https://github.com/jnunemaker/httparty/releases)) | `"~> 0.23.1"` → `"~> 0.24.0"` | ![age](https://developer.mend.io/api/mc/badges/age/rubygems/httparty/0.24.3?slim=true) | ![adoption](https://developer.mend.io/api/mc/badges/adoption/rubygems/httparty/0.24.3?slim=true) | ![passing](https://developer.mend.io/api/mc/badges/compatibility/rubygems/httparty/0.23.2/0.24.3?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/rubygems/httparty/0.23.2/0.24.3?slim=true) | --- ### Release Notes <details> <summary>jnunemaker/httparty (httparty)</summary> ### [`v0.24.3`](https://github.com/jnunemaker/httparty/releases/tag/v0.24.3) [Compare Source](https://github.com/jnunemaker/httparty/compare/v0.24.2...v0.24.3) **Full Changelog**: <https://github.com/jnunemaker/httparty/compare/v0.24.2...v0.24.3> #### Bug Fixes - Support the `json` gem 3.x, which removed the `quirks_mode` parser option. ([#&#8203;846](https://github.com/jnunemaker/httparty/issues/846)) - Fix the `MultiXml` deprecation warning with multi\_xml 0.9+. ([#&#8203;838](https://github.com/jnunemaker/httparty/issues/838), thanks [@&#8203;robzolkos](https://github.com/robzolkos)) - A UTF-8 byte order mark (BOM) is now stripped from responses that don't declare a charset. Before, a BOM-prefixed JSON response without a charset raised `JSON::ParserError`. ([#&#8203;852](https://github.com/jnunemaker/httparty/issues/852)) - A response body that is only a BOM, or a BOM followed by whitespace, now parses to `nil` like any other blank body, instead of raising or returning the whitespace. ([#&#8203;851](https://github.com/jnunemaker/httparty/issues/851), thanks [@&#8203;januththedev](https://github.com/januththedev)) - `parsed_response` and `response.body` are separate strings for UTF-8 text responses, as in 0.24.2. ([#&#8203;854](https://github.com/jnunemaker/httparty/issues/854)) #### Performance - `raise_on` with a Range (e.g. `500..599`) checks the range directly instead of building a regex for every code in it. ([#&#8203;843](https://github.com/jnunemaker/httparty/issues/843), thanks [@&#8203;MaxLap](https://github.com/MaxLap)) - Parsing allocates fewer objects per response. ([#&#8203;854](https://github.com/jnunemaker/httparty/issues/854)) #### Behavior Changes For `text/plain`, `text/html` and `text/csv` responses **without a charset**, a leading BOM is now removed from `parsed_response`, matching what already happened when `charset=utf-8` was set. If you worked around the BOM by matching it (for example a CSV header of `"\xEF\xBB\xBFid"`), that match will now be `"id"`. Workarounds like `delete_prefix("")` keep working. These are unchanged: `response.body` and `to_s` (raw bytes), `application/octet-stream` and other formats HTTParty doesn't parse, and bodies declared in other charsets such as ISO-8859-1 or UTF-16. #### Other - Specs no longer need a UTF-8 locale. ([#&#8203;853](https://github.com/jnunemaker/httparty/issues/853)) - README and example updates. ([#&#8203;836](https://github.com/jnunemaker/httparty/issues/836), thanks [@&#8203;harland-davis](https://github.com/harland-davis); [#&#8203;837](https://github.com/jnunemaker/httparty/issues/837), thanks [@&#8203;zed-0xff](https://github.com/zed-0xff)) ### [`v0.24.2`](https://github.com/jnunemaker/httparty/releases/tag/v0.24.2) [Compare Source](https://github.com/jnunemaker/httparty/compare/v0.24.1...v0.24.2) **Full Changelog**: <https://github.com/jnunemaker/httparty/compare/v0.24.1...v0.24.2> #### Bug Fixes - Streaming uploads are now opt-in - The streaming multipart upload feature introduced in 0.24.0 caused compatibility issues with some servers (returning 400 errors). Streaming is now disabled by default to preserve backwards compatibility. Enable it explicitly with stream\_body: true for memory-efficient large file uploads. ([#&#8203;832](https://github.com/jnunemaker/httparty/issues/832)) #### Example ```ruby # Default behavior (buffered, compatible with all servers) HTTParty.post('http://example.com/upload', body: { file: File.open('large.zip') }) # Opt-in to streaming for large files (reduced memory usage) HTTParty.post('http://example.com/upload', body: { file: File.open('large.zip') }, stream_body: true) ``` ### [`v0.24.1`](https://github.com/jnunemaker/httparty/releases/tag/v0.24.1) [Compare Source](https://github.com/jnunemaker/httparty/compare/v0.24.0...v0.24.1) #### What's Changed - Add trailing clrf when building header for non-file parts. by [@&#8203;serixscorpio](https://github.com/serixscorpio) in [#&#8203;833](https://github.com/jnunemaker/httparty/pull/833) #### New Contributors - [@&#8203;serixscorpio](https://github.com/serixscorpio) made their first contribution in [#&#8203;833](https://github.com/jnunemaker/httparty/pull/833) **Full Changelog**: <https://github.com/jnunemaker/httparty/compare/v0.24.0...v0.24.1> ### [`v0.24.0`](https://github.com/jnunemaker/httparty/releases/tag/v0.24.0) [Compare Source](https://github.com/jnunemaker/httparty/compare/v0.23.2...v0.24.0) #### What's Changed - Force binary encoding throughout by [@&#8203;jnunemaker](https://github.com/jnunemaker) in [#&#8203;823](https://github.com/jnunemaker/httparty/pull/823) - set Content-Type for Hash body in requests by [@&#8203;jnunemaker](https://github.com/jnunemaker) in [#&#8203;828](https://github.com/jnunemaker/httparty/pull/828) - feat: stream multipart file uploads to reduce memory usage by [@&#8203;jnunemaker](https://github.com/jnunemaker) in [#&#8203;829](https://github.com/jnunemaker/httparty/pull/829) - fix: prevent SSRF via absolute URL bypassing base\_uri by [@&#8203;jnunemaker](https://github.com/jnunemaker) in [#&#8203;830](https://github.com/jnunemaker/httparty/pull/830) **Full Changelog**: <https://github.com/jnunemaker/httparty/compare/v0.23.2...v0.24.0> </details> --- ### 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 this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi42Ni4wIiwidXBkYXRlZEluVmVyIjoiNDQuMTA5LjEiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbXX0=-->
Update dependency httparty to "~> 0.24.0"
All checks were successful
ci/woodpecker/push/test Pipeline was successful
Details
9959ce1cca
renovate force-pushed renovate/httparty-0.x from 9959ce1cca
All checks were successful
ci/woodpecker/push/test Pipeline was successful
Details
to 6370e595dc
All checks were successful
ci/woodpecker/push/test Pipeline was successful
Details
2026-07-15 21:02:12 +00:00 Compare
All checks were successful
ci/woodpecker/push/test Pipeline was successful
Details
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/httparty-0.x:renovate/httparty-0.x
git switch renovate/httparty-0.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 switch main
git merge --no-ff renovate/httparty-0.x
git switch renovate/httparty-0.x
git rebase main
git switch main
git merge --ff-only renovate/httparty-0.x
git switch renovate/httparty-0.x
git rebase main
git switch main
git merge --no-ff renovate/httparty-0.x
git switch main
git merge --squash renovate/httparty-0.x
git switch main
git merge --ff-only renovate/httparty-0.x
git switch main
git merge renovate/httparty-0.x
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
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
casper/bsky_handle_provider!52
No description provided.