From fd6231e61230b37e0e2408929ba4e20bdfc5c556 Mon Sep 17 00:00:00 2001 From: Graham Christensen Date: Thu, 6 Mar 2025 15:36:43 -0800 Subject: [PATCH] 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. --- .github/workflows/upload-release.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/upload-release.yml b/.github/workflows/upload-release.yml index 2eaf48d0e..b600dfba0 100644 --- a/.github/workflows/upload-release.yml +++ b/.github/workflows/upload-release.yml @@ -100,5 +100,5 @@ jobs: - uses: "DeterminateSystems/flakehub-push@main" with: rolling: ${{ github.ref == format('refs/heads/{0}', github.event.repository.default_branch) }} - visibility: "private" + visibility: "public" tag: "${{ github.ref_name }}"