Automated dependency updates #65
Labels
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Blocks
Depends on
#224 automated dev-ops workflows
fediversity/fediversity
#611 Update applications
fediversity/fediversity
#276 NixOS test of a deployment
fediversity/fediversity
#311 unify versioning (minus around nixops, for now)
fediversity/fediversity
Reference: fediversity/fediversity#65
Loading…
Add table
Add a link
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?
As a Fediversity maintainer,
I want for our packages to stay up to date with nixpkgs in an automated fashion,
so that we can offer security and feature updates without manually having to create merge requests for updates.
implementation notes
options seem:
kiara referenced this issue2025-04-07 18:39:27 +02:00
Automated flake inputs update with eg. RenovateBot?to Automated dependency updates with eg. RenovateBot?while a week has passed, i've yet to see a PR come out of this
Automated dependency updates with eg. RenovateBot?to Automated dependency updatesYour workflow seems to be running on the first day of the month, so we'll have to wait for beginning July to confirm.
Also, your workflow expects
ubuntu:latestfor which we don't have any runner, so nothing will happen ever (and knowing Forgejo you will not get notifications of this on acrontype of workflow).okay, i guess this needs configuring the runner (c.f. #356)?
as per a new run this fails on
nix-shellrelying on the nix path to have made a<nixpkgs>available.while an alternative could be to directly include the
npinspackage on the runner, that may imply a level of tight coupling of the runner with specific jobs (or dependency management libraries) that would seem not necessarily preferable.nix.nixPathto allow imperatively installing packages #399this seems to now get stuck on
Create PRstep'sgit remote prune origincommand, which would run indefinitely (initially left to run over an hour, a second time i gave up in a minute). an upstream search seems to reveal no similar issues, somehow.in this case it also seems less trivial to just 'unwrap' this action as we did for the previous one: they seem to run some huge js script.
updateworkflow use PR action actually meant for gitea #438uses, which resolved to data.forgejo.org/github.com #442uses#443unfortunately, the gitea fork of
create-pull-requestseems to similarly hang.that said, the command in question may matter only for
--force-with-lease(which afaik we don't use).that said, the invocation in question may also be the first invocation of
git.exec()in our execution path, so maybe something is up with that? definitely not the first git command in the CI run tho...git remote prune#444using a fork stripping that out, the PR step now yields this log.
this seems to at least progress further than before, altho it still just seems to hang somehow.
there's technically a commit decreasing verbosity on the action that could be reversed in a fork
if #463 converges on gerrit, that might overhaul this as well
lon advertises built-in PR creation including for forgejo.
(c.f. #302 - i'm not sure lon handles it for gerrit.)
edit: i may wanna find out if its PR creation (if it works) could be split off, for separation of concerns.
another approach i hadn't tried is the PR implementation of https://github.com/Mic92/update-flake-inputs-gitea
kiara referenced this issue2025-12-03 17:51:05 +01:00