CVE fixes and regular maintenance #552
Labels
No labels
FreeBSD
Kind/Breaking
Kind/Bug
Kind/Chore
Kind/DependencyUpdate
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Windows
linux-powerpc64le
linux-riscv64
linux-s390x
run-end-to-end-tests
run-forgejo-tests
run-multi-platform-tests
No milestone
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo/runner#552
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Aiming to make use of the
forgejo-runnerin a public instance, I'd be happy to see latest release being CVE free.Running
trivy fs .on this repo, I seerenovatealready detects these as pending updates. However, it would be good to get these in and released in regular intervals.Besides, a "vulnerability dashboard" (inspiration from Crow CI) as a pinned issue would help to see what is currently going on.
Agreed. The renovate dashboards:
are meant to propose updates when a direct dependency has a CVE that needs fixing. In this case it looks like none of them are. Which does not mean they don't deserve upgrading 😁
@viceice do you have an opinion?
For such cases we usally activate lockfile maintenance, which would update all transitive deps to latest versions. We do it on forgejo.
Checking why this doesn't work for go
":maintainLockFilesWeekly",Ah renovate by default doesn't propose updates to indirect deps. We can enable it.
golang.org/x/crypto v0.31.0 // indirectindirect
https://docs.renovatebot.com/modules/manager/gomod/
That's worth a try. There are ~60 of them, it is not overwhelming.
@earl-warren @viceice Is there any way I could help with reviewing/merging pending PRs?
sure, feel free to review open PRs
I meant to merge/review the pending sec PRs and eventually issue new releases. (Auto-merge is disabled for these in this repo.)
we need to check the renovate logs why those security fixes are not opened automatically. they are internally forced normally
Ok, it seems security updates can't override the disabled state. 🤔
let's see if this works
forgejo/renovate-config@4bff6dc36ahttps://docs.renovatebot.com/modules/manager/gomod/
i think this can now be closed?
Thanks for releasing an update.
My hopes are rather long-term, i.e. regular merges of important deps and (optionally) regular checks for CVEs using
trivyor another related CVE scanning tool. The dependency dashboard list in this repo is also quite large and I think there's still room for improvement ;) But I'll close here for now and hope this is addressed or will be in the future without bringing this up again.