Schedule the audit, the production backup and Renovate on Forgejo #496

New issue

admin-amaurycoudr · 2026-10-21T10:06:58Z

root commented

2026-10-21 10:06:58 +00:00

(Migrated from gitlab.core-project.space)

Parent

What to build

Nothing GitLab ran on a schedule is lost. Scheduled Forgejo workflows run the nightly dependency audit (also on lockfile changes), the nightly production database backup, and the weekly Renovate run with platform: forgejo and the bot's Renovate token, which only that job references. Each can also be started by hand. Renovate's config matches the Forgejo workflows instead of .gitlab-ci.yml.

Seam: a Forgejo Actions run (spec ## Seams).

Acceptance criteria

The audit runs nightly and on a lockfile change, and fails on a finding as it does today.
The production backup runs nightly and its restore procedure no longer names glab.
Renovate opens its weekly pull requests on Forgejo and updates the image pins in the Forgejo workflows.
Each workflow can be started by hand.

## Parent #489 ## What to build Nothing GitLab ran on a schedule is lost. Scheduled Forgejo workflows run the nightly dependency audit (also on lockfile changes), the nightly production database backup, and the weekly Renovate run with `platform: forgejo` and the bot's Renovate token, which only that job references. Each can also be started by hand. Renovate's config matches the Forgejo workflows instead of `.gitlab-ci.yml`. Seam: a Forgejo Actions run (spec `## Seams`). ## Acceptance criteria - [ ] The audit runs nightly and on a lockfile change, and fails on a finding as it does today. - [ ] The production backup runs nightly and its restore procedure no longer names `glab`. - [ ] Renovate opens its weekly pull requests on Forgejo and updates the image pins in the Forgejo workflows. - [ ] Each workflow can be started by hand.

root commented

2026-10-21 10:07:19 +00:00

(Migrated from gitlab.core-project.space)

mentioned in issue #498