defunkt / hurl

Hurl makes HTTP requests.
http://hurl.it
MIT License
531 stars 77 forks source link

Bump yajl-ruby from 0.7.8 to 1.4.2 #60

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps yajl-ruby from 0.7.8 to 1.4.2.

Changelog

Sourced from yajl-ruby's changelog.

Changelog

1.1.0 (November 9th, 2011)

  • fix compilation due to a "bug" in gcc-llvm on 10.7.2
  • fix gemspec so ruby 1.8.6 or later is required

1.0.0 (September 13th, 2011)

  • add deprecation notice for Yajl's Bzip2 support
  • add deprecation notice for Yajl's Deflate support
  • add deprecation notice for Yajl's Gzip support
  • add deprecation notice for Yajl's JSON gem compatibility API
  • add deprecation notice for Yajl::HttpStream
  • change the path the extension is copied into to be 'lib/yajl'
  • remove 'ext' from the loadpath

0.8.3 (August 16th, 2011)

  • fix bug where Yajl::HttpStream wouldn't pass through a user-specified socket
  • fix incorrect Ruby initialization hook method name
  • Bump bundled YAJL version to 1.0.12
  • fix to correctly symbolize multibyte characters on 1.9
  • add :headers option to Yajl::HttpStream for user-specified arbitrary headers

0.8.2 (March 22nd, 2011)

  • define RSTRING_NOT_MODIFIED for rbx to prevent string caching, making things A LOT faster (100x)

0.8.1 (February 11th, 2011)

  • fixed a retart bug where Yajl::VERSION wasn't defined when explicitly requiring yajl/http_stream

0.8.0 (February 2nd, 2011)

  • added a new html_safe option to Yajl::Encoder to escape '/' characters for use in the DOM
  • moved away from Jeweler to a Bundler/manual gemfile management setup

0.7.9 (January 11th, 2011)

  • moved to rspec2
  • fixed some compilation warnings on 1.9.3
  • brought over latest from Yajl upstream
  • finally removed the deprecated Yajl::Stream methods
  • moved to rake-compiler
  • moved to Bundler for development
  • fix memory corruption bug when using :pretty => true and a custom indent string
  • fixed memory leak when exceptions were being raised during a parse
Commits


Dependabot compatibility score

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 rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/defunkt/hurl/network/alerts).
dependabot[bot] commented 2 years ago

Superseded by #61.