Skip to content

Ensure cargo is always up-to-date for openvasd #579

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

Merged
merged 1 commit into from
Jun 19, 2025
Merged

Conversation

bjoernricks
Copy link
Contributor

What

Ensure cargo is always up-to-date for openvasd

Why

Distributions may ship with an too old cargo version for openvasd. Therefore update cargo to the latest stable version via rustup.

References

https://forum.greenbone.net/t/openvasd-build-fails/21340/6

Checklist

@bjoernricks bjoernricks requested a review from a team as a code owner June 11, 2025 08:23
Copy link

github-actions bot commented Jun 11, 2025

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Snapshot Warnings

⚠️: No snapshots were found for the head SHA 1f05885.
Ensure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice.

OpenSSF Scorecard

PackageVersionScoreDetails

Scanned Files

@greenbonebot greenbonebot enabled auto-merge (rebase) June 11, 2025 08:23
Distributions may ship with an too old cargo version for openvasd.
Therefore update cargo to the latest stable version via rustup.
@greenbonebot greenbonebot merged commit 505d27c into main Jun 19, 2025
4 checks passed
@greenbonebot greenbonebot deleted the use-rustup branch June 19, 2025 09:38
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