-
plowsof.merge+ 2474
-
xmr-prAdded
-
m-relay<ofrnxmr:xmr.mx> plowsof, noticed the versions in that workflow are 1800, should they be 1840?
-
plowsofcan't hurt , we're just using the gui's built-in auto update verify tool ..... a 'grab latest tag' so it's not hard coded can be a todo
-
m-relay<ofrnxmr:xmr.mx> Yeah, not for this pr, just curious
-
plowsoflets see if this works stackoverflow.com/a/67404585
-
plowsofcurl "api.github.com/repos/monero-project/monero-gui/tags" | jq -r '.[0].name'
-
plowsofoh ok, so its using v18.0.0 to verify latest tag. v18.0.0 is "known working" , if the verify is broke in the new tag, then it could cause confusion, but we'd also like to know if it where broken.. hm
-
plowsofofrnxmr
-
m-relay<ofrnxmr:xmr.mx> You can also check releases, idk whata better tho
-
m-relay<ofrnxmr:xmr.mx> `curl -ls "api.github.com/repos/$project/$repo/releases/latest" | jq -r '.tag_name'`
-
m-relay<ofrnxmr:xmr.mx> Nodo (used to) do this
-
selstaplowsof: you need at least one before latest
-
selstaideally you want to know if the previous version can show that a new release is out
-
plowsofAh i see, thanks selsta
-
selstabecause the newest version wouldn't update to itself
-
selstabinaryFate: everything is ready for DNS update
-
m-relay<ofrnxmr:xmr.mx> zerobin.net/?3285d1bc3f4412a5#m4AD/…kTCUjovnI4es4jdDd/ePmEPR+hCLybk/vw= plowsof
-
plowsofjust trying to run a similar patch to test , thanks xD
-
plowsof.merge+ 2475
-
xmr-prAdded