bugs/e4381a232798f2c1a0e46f13a8c6aea70dd5b763
stuebinm 2022-02-01 14:50:19 +01:00
commit e4381a2327
4 changed files with 2 additions and 0 deletions

0
create-clock-7 Normal file
View File

0
edit-clock-17 Normal file
View File

1
ops Normal file
View File

@ -0,0 +1 @@
{"version":1,"ops":[{"type":1,"author":{"id":"15c9d6c01e34fec0e7f1559c86cbbdd66d9dc10c"},"timestamp":1643723419,"title":"update workflow: how to not forget dependencies?","message":"[this is more of a discussion issue, I think]\n\nGiven that I've just updated all of our non-nixpkgs dependencies that themselves\nhave versions corresponding to nixpkgs's (i.e. everything but non-nix things and \nhxchn's nixfiles) since we apparently forgot all of them the first time round, I \nthink it might be worth to try and come up with some way of not forgetting that\nduring next version upgrade (can we somehow \"couple\" versions using niv / \nsomething else? Just write a reminder somewhere?)","files":null}]}

1
root Normal file
View File

@ -0,0 +1 @@
{"version":1,"ops":[{"type":1,"author":{"id":"15c9d6c01e34fec0e7f1559c86cbbdd66d9dc10c"},"timestamp":1643723419,"title":"update workflow: how to not forget dependencies?","message":"[this is more of a discussion issue, I think]\n\nGiven that I've just updated all of our non-nixpkgs dependencies that themselves\nhave versions corresponding to nixpkgs's (i.e. everything but non-nix things and \nhxchn's nixfiles) since we apparently forgot all of them the first time round, I \nthink it might be worth to try and come up with some way of not forgetting that\nduring next version upgrade (can we somehow \"couple\" versions using niv / \nsomething else? Just write a reminder somewhere?)","files":null}]}