ci: pin Nixpkgs for deployments #310
No reviewers
Labels
No labels
automation
backend
bug
contributor experience
data
deployment
documentation
duplicate
good first issue
help wanted
nice to have
notifications
package maintainer
performance
skin
tech debt
user story
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-community/nix-security-tracker#310
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "pin-nixpkgs-deployment"
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?
this doesn't rely on NIX_PATH and is therefore fully pure, and uses our
own, controlled dependencies.
the Nixpkgs for deployment currently not decoupled from the one for
development because the build is broken on the newest version.
we still need a policy for how to run updates, but ideally we'd use
exactly one version of Nixpkgs for everything.
This doesn't pass CI though.
Nothing passes CI at the moment because we can't build the server against unstable.
That's not the error.
Le jeu. 31 oct. 2024, 20:38, Valentin Gagarin @.***> a
écrit :
The dry activations check is expected to fail because it runs in the base branch's context (it's has a
pull_request_target
trigger). It should unbreak once this change is merged.