Bump github.com/go-resty/resty/v2 from 2.13.1 to 2.15.3

[dependabot[bot]]

Bumps github.com/go-resty/resty/v2 from 2.13.1 to 2.15.3.

Release notes

Sourced from github.com/go-resty/resty/v2's releases.

v2.15.3

Release Notes

Bug Fixes

• fix: 'invalid memory address or nil pointer dereference' in response logger by @​matlockx in go-resty/resty#872

Documentation

• For release v2.15.3 by @​jeevatkm in go-resty/resty#874

New Contributors

• @​matlockx made their first contribution in go-resty/resty#872

Full Changelog: https://github.com/go-resty/resty/compare/v2.15.2...v2.15.3

v2.15.2

Release Notes

Bug Fixes

• fix: do not use errors.Join, just use custom error approach by @​jeevatkm in go-resty/resty#863

Documentation

• release: version bump and readme update for v2.15.2 by @​jeevatkm in go-resty/resty#864

Full Changelog: https://github.com/go-resty/resty/compare/v2.15.1...v2.15.2

v2.15.1

Release Notes

Bug Fixes

• fix: do not parse response debug log with correct text by @​jeevatkm in go-resty/resty#858

Documentation

• for v2.15.1 release by @​jeevatkm in go-resty/resty#859

Full Changelog: https://github.com/go-resty/resty/compare/v2.15.0...v2.15.1

v2.15.0

Release Notes

New Features

• feat: add max reponse body limit by @​trim21 in go-resty/resty#830
• feat: add SetClientRootCertificate method support clientCAs usage by @​MagHErmit in go-resty/resty#826

Enhancements

• feat: add ability to set custom multipart boundary value by @​PokeGuys in go-resty/resty#820
• feat(refactor): for pr #826 by @​jeevatkm in go-resty/resty#848

Bug Fixes

... (truncated)

Commits

• bea44b7 chore: for release v2.15.3 (#874)
• e11af35 fix: invalid memory address or nil pointer dereference in response logger (#872)
• 231ca0e release: version bump and readme update for v2.15.2 (#864)
• ce7695b fix: do not use errors.Join, just use custom error approach (#863)
• 5d33e1a for v2.15.1 release (#859)
• fc89165 fix: do not parse response debug log with correct text (#858)
• 321cab9 release: version bump and readme update for v2.15.0 (#852)
• 8e6cfc2 docs: godoc improvements (#851)
• aa7c48e doc: godoc improvements and corrections (#849)
• e49dd06 feat(refactor): for pr #826 (#848)
• 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 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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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)

[zalando-compr-opensource[bot]]

invalid team ID

The team ID in your .zappr.yaml file does not appear to be valid. Please, fix this before team ID checks will be added back into ComPR's specification check.

You can follow this guideline for help.

[zalando-compr-opensource[bot]]

invalid team ID

The team ID in your .zappr.yaml file does not appear to be valid. Please, fix this before team ID checks will be added back into ComPR's specification check.

You can follow this guideline for help.

[zalando-compr-opensource[bot]]

invalid team ID

The team ID in your .zappr.yaml file does not appear to be valid. Please, fix this before team ID checks will be added back into ComPR's specification check.

You can follow this guideline for help.

[mikkeloscar]

:+1: