chore: nix-config-private lock bump (automated CD) #1964
No reviewers
Labels
No labels
backlog
bug
enhancement
in-progress
review
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ymrtech/nix-config!1964
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "priv-lock-7eadff4"
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?
Automated flake.lock bump from ymrtech/nix-config-private CI/CD. Affects: scripts/kanboard/**. Merged BEFORE deploy (merge-then-deploy): the pin carries main PLUS the current client peer set, so the deployed tree is never missing either; the deploy below is the merge push-triggered NixOS Deploy on main.
Opened by hand (card nix-config#929) because the chain's own run for this rev refused at its first step:
ci.ymlon nix-config-private@7eadff42 is red ONLY at the tail of theEval real host configs with this revisionjob, where theDispatch CD chain (main only)step gets403 token does not have at least one of required scope(s): [write:repository]from the runner-pool.netrc(the pool includes a[ci]slot whose runner home has no working write:repository token - the family tracked by cards nix-config#918 / #907). Every evaluation in that job passed and all other 27 statuses on the head sha are green, so the merge itself is sound; the chain's gate is permanent for a sha with a red status because Forgejo exposes no re-run API. The command, branch name, commit message, PR title and body here mirror the chain's step 1-3 exactly, so a later chain run for a newer rev simply moves the pin onward.