-
Notifications
You must be signed in to change notification settings - Fork 15
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.
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
1.0
& nixpkgs release
#204
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Regarding release version of The caller can now override the omnix invocation as of d25eab3 Once we release 1.0 to nixpkgs, we can host the stable When we release 1.1, we repeat the same process, allowing existings projects on 1.0 to remain unimpacted until they explicitly upgrade to 1.0 (by changing the URL and hash in their |
requires #427 |
This is interesting. I wonder if we can revert the ![]() |
Should I tag after merging #430 - or do we need anything else for nixpkgs upstreaming? Let me know. |
Avoids the need to explicitly define—and later maintain—these ENVs in nixpkgs while packaging for #204. requires juspay/rust-flake#33
Before release
See sub-issues below for pending work.
Upstream
pkgs.omnix
to nixpkgsom
binary (notomnix-cli
).om ci run --on ssh://...
works.The text was updated successfully, but these errors were encountered: