Add a scheduled flake.lock update job #68
Labels
No labels
automation
automerge
ci
infra
migrated/beads
priority/P2
refactoring
repo-maintenance
status/in-progress
testing
type/epic
type/task
automerge
bug
dependencies
duplicate
help wanted
invalid
lang
rust
migrations
opencode
question
security
type
documentation
type
enhancement
type
maintenance
type
refactor
vulnerability
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Reference
Personal/cluster#68
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?
Add a scheduled automation job that updates the flake lock file.
Acceptance criteria
A scheduled workflow opens or applies flake input updates using the repository's established automation conventions.
Closure reason
Already handled by Renovate, which opens weekly pull requests updating flake.lock.
Beads migration
Original ID:
cluster-uye· Status:closed· Priority: P2 · Type: taskOriginal timestamps and metadata are preserved below; Forgejo's native timestamps reflect the migration.
Original Beads record
Relationships
Related issue: #67 (Beads
related).