Bump oauthlib from 3.2.0 to 3.2.1 #2434
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
dependencies
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
|
@nautobot/core This is coming in via |
Bumps [oauthlib](https://github.com/oauthlib/oauthlib) from 3.2.0 to 3.2.1. - [Release notes](https://github.com/oauthlib/oauthlib/releases) - [Changelog](https://github.com/oauthlib/oauthlib/blob/master/CHANGELOG.rst) - [Commits](oauthlib/oauthlib@v3.2.0...v3.2.1) --- updated-dependencies: - dependency-name: oauthlib dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/pip/oauthlib-3.2.1
branch
from
a3afb7a
to
0a132a8
Compare
This seems like a horrible idea to me.... If we are using poetry for dependency management we shouldn't use pip to upgrade... I feel like if you want to recommend something we should recommend |
Poetry isn't documented to manage dependencies for end-users. Our installation documentation specifically says Since this is a dependency of a dependency installations won't automagically upgrade the version when they upgrade Nautobot unless we require it as a minimum version. The |
|
@dependabot rebase |
|
Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry! If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request |
Bumps oauthlib from 3.2.0 to 3.2.1.
Release notes
Sourced from oauthlib's releases.
Changelog
Sourced from oauthlib's changelog.
Commits
88bb156Updated date and authors1a45d97Prepare 3.2.1 release0adbbe1docs: fix typos6569ec3docs: Fix a few typosbdc486eFixed isort imports7db45bdFix typo in server.rstb14ad85chore: s/bode_code_verifier/body_code_verifier/gb123283Allow non-HTTPS issuer when OAUTHLIB_INSECURE_TRANSPORT. (#803)2f887b5Docs: fix Sphinx warnings for better ReadTheDocs generation (#807)d4bafd9Merge pull request #797 from cclauss/patch-2Dependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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 labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and languageYou can disable automated security fix PRs for this repo from the Security Alerts page.