marvin8/yunjin
Watch
1
0
Fork
You've already forked yunjin
 0
Code Issues 7 Pull requests Releases Activity Actions

Weekly checks Forgejo action (dependency freshness and advisories) #39

New issue
Open
opened 2026-09-13 02:12:23 +00:00 by agent-pi · 1 comment
agent-pi commented 2026-09-13 02:12:23 +00:00
Collaborator
Copy link

Problem

CI runs nox only on PRs and pushes. Between pushes, dependency drift keeps happening: new versions ship, new advisories are published, and nothing notices until the next PR.

Goal

A scheduled weekly Forgejo action that runs the drift-catchers (pysentry advisories, zaojun freshness) against main, so staleness surfaces on its own schedule.

## Problem CI runs nox only on PRs and pushes. Between pushes, dependency drift keeps happening: new versions ship, new advisories are published, and nothing notices until the next PR. ## Goal A scheduled weekly Forgejo action that runs the drift-catchers (pysentry advisories, zaojun freshness) against `main`, so staleness surfaces on its own schedule.
agent-pi commented 2026-09-13 02:12:51 +00:00
Author
Collaborator
Copy link

Findings

  • cang already runs this exact pattern: .forgejo/workflows/weekly-checks.yml — schedule: cron "13 16 * * 5" (Fridays 16:13 UTC) plus workflow_dispatch, checkout, astral-sh/setup-uv@v5, uv sync --all-groups, then uv run nox -s pysentry zaojun.
  • yunjin's noxfile already defines both sessions (pysentry, zaojun), so the weekly run needs no new tooling — only the workflow file.
  • yunjin's CI runner is zhuiri (cang uses suanni); the cron minute should differ from cang's so the two scheduled runs don't land on the runner simultaneously.

Plan of attack

  1. New .forgejo/workflows/weekly-checks.yml mirroring cang's: weekly cron (offset from cang's slot) + workflow_dispatch, runner zhuiri, uv sync --all-groups, uv run nox -s pysentry zaojun.
  2. Verification: workflow_dispatch manual run green; failures visible as a failed scheduled run on main.

Branch

feat/weekly-checks-action

Commit

  1. :construction_worker: Add weekly dependency and advisory checks
## Findings - cang already runs this exact pattern: `.forgejo/workflows/weekly-checks.yml` — `schedule: cron "13 16 * * 5"` (Fridays 16:13 UTC) plus `workflow_dispatch`, checkout, `astral-sh/setup-uv@v5`, `uv sync --all-groups`, then `uv run nox -s pysentry zaojun`. - yunjin's noxfile already defines both sessions (`pysentry`, `zaojun`), so the weekly run needs no new tooling — only the workflow file. - yunjin's CI runner is `zhuiri` (cang uses `suanni`); the cron minute should differ from cang's so the two scheduled runs don't land on the runner simultaneously. ## Plan of attack 1. New `.forgejo/workflows/weekly-checks.yml` mirroring cang's: weekly cron (offset from cang's slot) + `workflow_dispatch`, runner `zhuiri`, `uv sync --all-groups`, `uv run nox -s pysentry zaojun`. 2. Verification: `workflow_dispatch` manual run green; failures visible as a failed scheduled run on `main`. ## Branch `feat/weekly-checks-action` ## Commit 1. `:construction_worker: Add weekly dependency and advisory checks`
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
0.4.0
0.3.0
0.2.0
0.1.0
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
marvin8/yunjin#39
No description provided.