Publish w/o nix #388
Merged
Publish w/o nix #388
Conversation
This file contains 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
aljazerzen
approved these changes
Feb 21, 2025
|
Yeah, half the point of the nix was that the whole env would be cached. I don't know why it does not work as it should, so I agree to just axe it all together. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The nix caching services are no longer easy to access and publishes are taking ~20 mins. This swaps out the nix publishing process for a standard Rust publishing process.
Each script now uses a standard body so we can more easily update the body of the publishing script. The tag name determines the project name environment variable.