Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update module github.com/go-resty/resty/v2 to v2.15.2 #127

Merged
merged 1 commit into from
Sep 22, 2024

Conversation

bakito
Copy link
Owner

@bakito bakito commented Sep 22, 2024

This PR contains the following updates:

Package Type Update Change
github.com/go-resty/resty/v2 require patch v2.15.1 -> v2.15.2

Release Notes

go-resty/resty (github.com/go-resty/resty/v2)

v2.15.2

Compare Source

Release Notes

Bug Fixes

Documentation

Full Changelog: go-resty/resty@v2.15.1...v2.15.2


Configuration

📅 Schedule: 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 Renovate Bot.

@coveralls
Copy link

Pull Request Test Coverage Report for Build 10978129031

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 79.355%

Totals Coverage Status
Change from base Build 10953335144: 0.0%
Covered Lines: 246
Relevant Lines: 310

💛 - Coveralls

@bakito bakito merged commit 65af350 into main Sep 22, 2024
2 checks passed
@bakito bakito deleted the renovate/git.luolix.top-go-resty-resty-v2-2.x branch September 22, 2024 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants