Skip to content
This repository has been archived by the owner on Sep 2, 2021. It is now read-only.

Bump rest-assured from 4.3.0 to 4.4.0 #275

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps rest-assured from 4.3.0 to 4.4.0.

Changelog

Sourced from rest-assured's changelog.

Changelog 4.4.0 (2021-05-21)

  • Upgrading kotlin extension module to use Kotlin 1.5.0 (previously 1.4.21 was used)

  • Upgrading commons-io from 2.4.0 to 2.8.0

  • Apache http client is upgraded from 4.5.3 to 4.5.13 (thanks to Daniel Reissenberger for pull request)

  • Improved oauth compatibility with new http client

  • Fixed a bug in EncoderConfig where user configured was accidentally set to true in default constructor

  • Non-backward compatible change: REST Assured will no longer add "charset=utf-8" by default to application/json content-type's since this is not recommended by RFC 7159. REST Assured will still automatically encode content as UTF-8, it's just that the charset is not added. To revert to the old behavior do:

    RestAssured.config(RestAssured.config().encoderConfig(EncoderConfig.encoderConfig().defaultCharsetForContentType("UTF-8", "application/json")))

    or specify the charset explicitly in the request:

    given().contentType(ContentType.JSON.withCharset(UTF_8)). .. (thanks to Michal Domagala for initial pull request)

  • Added MULTIPART to as an option ContentType (thanks to Yusuf Tayman for pull request)

  • Upgraded groovy from 3.0.7 to 3.0.8

Changelog 4.3.3 (2020-12-11)

  • Upgrading kotlin extension module to use Kotlin 1.4.21 (previously 1.4.10 was used)
  • Upgraded groovy from 3.0.6 to 3.0.7
  • Ensure subclasses of ResponseOptions do not break Prettifier (#1425) (thanks to Sam Neirinck for PR)

Changelog 4.2.1 (2020-12-11)

  • Backport of: Fix content type name before charset recognition (#1341)

Changelog 4.3.2 (2020-11-08)

  • Upgrade json-schema-validator to 2.2.14 (issue 1397) (thanks to Guillaume Smet for PR)

  • Upgrading apache commons lang3 from 3.4 to 3.11.

  • Added asPrettyString method to ResponseBody (issue 1395) (thanks to GithubMood for PR)

  • Describe non matching actual method with Hamcrest matcher format (issue 1387) (thanks for Ivo Šmíd for PR) Before you could run into cryptic error messages such as:

    JSON path values.pi doesn't match.
    Expected: <3.14>
    Actual: 3.14
    

    Now, you see this instead:

    JSON path values.pi doesn't match.
    Expected: <3.14>
    Actual: <3.14F>
    
  • Upgraded groovy from 3.0.3 to 3.0.6

  • Upgrading Kotlin extension module to use Kotlin 1.4.10 (previously 1.3.72 was used)

Changelog 4.3.1 (2020-07-03)

... (truncated)

Commits
  • 275df07 [maven-release-plugin] prepare release rest-assured-4.4.0
  • cd3fdc1 Updated changelog to prepare for new release
  • 74b998d Use java 16 instead of ea
  • d227806 Upgraded groovy from 3.0.7 to 3.0.8
  • c47822b Changing restlet dependency to avoid having a third-party maven repo
  • 17ce73e Fixed several failing tests as well as refined logic for determining charset ...
  • ae7432c Charset is not added to application/json by default in spring-mock-mvc
  • 6b53cbe Updated changelog to reflect latest changes [ci skip]
  • 5291cf1 Added new content type multi-part (#1473)
  • 1cdb73c REST Assured will no longer add "charset=utf-8" by default to application/jso...
  • Additional commits viewable in compare view

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
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label May 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants