@abathur:matrix.org / @matthewkenigsberg:matrix.org Would it be possible to get a new release into the prerelease branch at some point before our next meeting? We've been seeing an uptick of issues reported on our repo despite being installed from the experimental repo at the behest of devenv docs (likely because the old version currently in the prerelease branch doesn't have the proper cargo metadata set so errors are still being told to file issues against DetSys instead of the experimental installer)

Looking at this now. Good news, I think.

It looks like the workflow that updates prerelease ~would have automatically picked up our May bump if we hadn't clobbered hydraJobs.build in the process :)

https://github.com/NixOS/experimental-nix-installer/commit/4993d8c94679087033ed9df327e44ac4773df38b#diff-206b9ce276ab5971a2489d75eb1b12999d4bf3843b7988cbe8d687cfde61dea0L208

I should be able to restore that easily enough as long as the builds succeed, but I'm hoping Matthew Kenigsberg can take a peek and maybe remember if there was a reason to drop the attr or if this was just an oops during conflict resolution?

(Eval ran okay when I pointed hydra at a fix branch; not sure how quickly it will get to the first build. It looks like the "Generate Installer Script" job got disabled for 60-days of repo inactivity over the summer, so it won't automatically start picking up the new eval until we enable it. I'm building #.hydraJobs.build.x86_64-darwin locally as a sanity check but I don't think it'll fail.)

Looking at this now. Good news, I think.

It looks like the workflow that updates prerelease ~would have automatically picked up our May bump if we hadn't clobbered hydraJobs.build in the process :)

https://github.com/NixOS/experimental-nix-installer/commit/4993d8c94679087033ed9df327e44ac4773df38b#diff-206b9ce276ab5971a2489d75eb1b12999d4bf3843b7988cbe8d687cfde61dea0L208

I should be able to restore that easily enough as long as the builds succeed, but I'm hoping Matthew Kenigsberg can take a peek and maybe remember if there was a reason to drop the attr or if this was just an oops during conflict resolution?

(Eval ran okay when I pointed hydra at a fix branch; not sure how quickly it will get to the first build. It looks like the "Generate Installer Script" job got disabled for 60-days of repo inactivity in September, so it won't automatically start picking up the new eval until we enable it. I'm building #.hydraJobs.build.x86_64-darwin locally as a sanity check but I don't think it'll fail.)

In reply to @abathur:matrix.org
well, I'll try to remember to :]

Domen Kožar: Cole identified the bug in assemble_installer.py that was keeping it from updating, but the scheduled workflow now fails when the git-auto-commit action tries to check out the prerelease branch because the branch now has a set of binary files that conflict with the uncommitted copies that the workflow has built against main.

Well beyond out of time to poke at it for the day, so I'm hoping you can take a look :)