Skip to content

Fix/cachix pin no response - follow up #4910

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
juliankuners merged 1 commit into from
Apr 15, 2026
+3 −3
Merged

Fix/cachix pin no response - follow up #4910

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,9 +94,9 @@ jobs:

# Publish all three package variants using kup publish
# Using public macOS runner has proven reliable for large file uploads
kup publish --verbose k-framework-binary .#k --keep-days 180
kup publish --verbose k-framework-binary .#k.openssl.secp256k1 --keep-days 180
kup publish --verbose k-framework-binary .#k.openssl.procps.secp256k1 --keep-days 180
kup publish --verbose k-framework-binary .#k --keep-days 180 || true
kup publish --verbose k-framework-binary .#k.openssl.secp256k1 --keep-days 180 || true
kup publish --verbose k-framework-binary .#k.openssl.procps.secp256k1 --keep-days 180 || true

# kup/cachix pin visibility can be flaky; verify pins and narinfo via public API
bash .github/scripts/check-cachix-pin.sh
Expand Down
Loading