-
Notifications
You must be signed in to change notification settings - Fork 5
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
build(deps): Bump httpoison from 2.1.0 to 2.2.0 #42
Conversation
Bumps [httpoison](https://github.com/edgurgel/httpoison) from 2.1.0 to 2.2.0. - [Release notes](https://github.com/edgurgel/httpoison/releases) - [Commits](edgurgel/httpoison@v2.1.0...v2.2.0) --- updated-dependencies: - dependency-name: httpoison dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Codecov Report
@@ Coverage Diff @@
## main #42 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 2 2
Lines 34 34
=========================================
Hits 34 34 📣 Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @dependabot 👌
👋 Hey, I'm trying to use this library and getting an error in resolving dependencies:
I think maybe this PR wasn't released, but I also think maintaining dependencies in a library is different than in an app. In an app you'd want to use something like dependabot to make sure you're (almost) always using the latest versions, but in a library your requirements become the requirements of the applications which use this library. So probably you should have something like Thanks very much |
Something to clarify depending on your background: if you've used Node.js, for example, even library gets its own copy of dependencies, so an application might have a lot of different versions of the same transient dependency nested inside of the |
We may need to exclude HTTPoison from @dependabot updates ... 💭 |
👍 Thanks! I would do the same with |
Bumps httpoison from 2.1.0 to 2.2.0.
Release notes
Sourced from httpoison's releases.
Commits
8040bdb
Bump versiond22f1b1
Update README.md0b8c71a
fix test failures due to map key ordering24a3908
Keep location in HTTPoison.Base.using/15920e19
Updates hackney to 1.20.1 to include a fix for path encoding.b562a28
Fix formatting errors on the docb2d4438
[Format] Fix formatting warning6fe3b1c
add test for request112ceb5
Add the request!/1 function711093f
Update README.md: httparrot -> postman-echoDependabot 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 <dependency name> 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)