-
Notifications
You must be signed in to change notification settings - Fork 1
Bump pyo3 from 0.13.2 to 0.17.3 in /src/rust #91
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
Conversation
Bumps [pyo3](https://github.com/pyo3/pyo3) from 0.13.2 to 0.17.3. - [Release notes](https://github.com/pyo3/pyo3/releases) - [Changelog](https://github.com/PyO3/pyo3/blob/main/CHANGELOG.md) - [Commits](PyO3/pyo3@v0.13.2...v0.17.3) --- updated-dependencies: - dependency-name: pyo3 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Mode: paranoid | Total findings: 56 | Considered vulnerability: 56 Insecure Use of Dangerous Function (4)
More info on how to fix Insecure Use of Dangerous Function in C/C++. Insecure Access Control (1)
More info on how to fix Insecure Access Control in C/C++. Vulnerable Libraries (1)
More info on how to fix Vulnerable Libraries in Rust. Hard-Coded Secrets (50)
More info on how to fix Hard-Coded Secrets in General. 👉 Go to the dashboard for detailed results. 📥 Happy? Share your feedback with us. |
Superseded by #94. |
Bumps pyo3 from 0.13.2 to 0.17.3.
Release notes
Sourced from pyo3's releases.
... (truncated)
Changelog
Sourced from pyo3's changelog.
... (truncated)
Commits
a3edbf4
release: 0.17.3062470a
Fix module name in getting started5bbd21c
DisablePyModule::filename
on PyPy522ac1c
Run Rust tests using Valgrind and cargo-careful (#2706)47540b8
packaging: support Python 3.1164f52c6
add internal release notes8088af3
Avoid calling slice::from_raw_parts with a null pointerb6f17aa
Update getting_started.md7647b70
Point new users at specific source file for Rust code.e48525f
Add more implementations of ExactSizeIterator when iterating built-in Python ...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)