revert: ci: use ubuntu-latest for release workflow (#282)#283
Merged
Conversation
This reverts commit 4dad26a. This commit switched to using ubuntu-latest for the release workflow instead of dealing with firewall issues on the blitzar vm runner. However, the release workflow now takes over an hour, because it needs to build cuda from scratch when entering the nix environment instead of taking advantage of the nix store (cache) on the blitzar vm runner. It will likely be faster to just squash the firewall issues.
stuarttimwhite
approved these changes
Jun 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale for this change
This reverts commit 4dad26a. This commit switched to using ubuntu-latest for the release workflow instead of dealing with firewall issues on the blitzar vm runner. However, the release workflow now takes over an hour, because it needs to build cuda from scratch when entering the nix environment instead of taking advantage of the nix store (cache) on the blitzar vm runner. It will likely be faster to just squash the firewall issues.
What changes are included in this PR?
Are these changes tested?
These changes do not affect existing functionality, which should be verified by existing tests.