Graham Christensen fd6231e612 Publish the flake as public, every time ... This exposed a bug in FlakeHub's private toggling, where the public 3.0.0 release followed by an accidentally private 0.1.x release, managed to cause the flake to be shunted closed. This should not be possible, so let's dig into how that came to be and make sure to create a test case against this should-be-impossible transition.		2025-03-06 15:36:43 -08:00
..
build.yml	Setup uploading PRs, tags, and branches to IDS	2025-02-21 13:01:26 -08:00
ci.yml	Run all VM tests	2025-02-26 17:42:37 +01:00
labels.yml	Revert "wip: delete unnecessary CI for now"	2025-02-21 13:02:04 -08:00
propose-release.yml	Fixup propose-release: don't puke if the version number didn't change	2025-03-05 10:09:06 -08:00
test.yml	Revert "wip: delete unnecessary CI for now"	2025-02-21 13:02:04 -08:00
upload-release.yml	Publish the flake as public, every time	2025-03-06 15:36:43 -08:00