ci: build the okf package explicitly — flake check skips package builds - #8
Merged
Conversation
Verified on the first cached runs (2026-07-12): nix flake check builds only checks.* (okf-tests + the node_modules FOD reached the cache) and reports packages as 'build skipped', so the okf binary itself was never pushed. nix build .#okf puts the actual artifact in the cache on both platforms.
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
1 participant
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.
Follow-up to #7, found while verifying the cache:
nix flake checkbuilds checks only — the runs pushedokf-testsand thenode_modulesFOD (both verified fetchable from cache.flakehub.com), but reportedpackages.*.okfas build skipped, so the binary consumers actually run never entered the cache. One explicitnix build .#okf -Lfixes that on both platforms.