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

ci(megalinter): re-enable trivy #449

Merged
merged 1 commit into from
Dec 3, 2024
Merged

ci(megalinter): re-enable trivy #449

merged 1 commit into from
Dec 3, 2024

Conversation

AtomicFS
Copy link
Collaborator

@AtomicFS AtomicFS requested a review from MDr164 as a code owner November 28, 2024 20:58
@AtomicFS AtomicFS enabled auto-merge November 28, 2024 20:58
@github-actions github-actions bot added testing Testing related bugfix Bugfix / fix labels Nov 28, 2024
- the issue seems to be fixed upstream
- this reverts commit f024bc6

Signed-off-by: AtomicFS <[email protected]>
@AtomicFS AtomicFS added this pull request to the merge queue Dec 3, 2024
Merged via the queue into main with commit 17b231c Dec 3, 2024
42 checks passed
@AtomicFS AtomicFS deleted the fix/trivy branch December 3, 2024 11:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugfix Bugfix / fix testing Testing related
Projects
None yet
Development

Successfully merging this pull request may close these issues.

re-enable trivy linter once the upstream issue with DB is fixed
2 participants