Chore/release packaging - #347
Merged
Merged
Conversation
The core-module alias blocks only surfaced the dev `lgx` / `install` outputs, so `nix build .#amm-module-lgx-portable` (the variant you distribute) didn't resolve. Add the `-portable` aliases for both amm_module and token_module, mirroring the UI package aliases. mkLogosModule already produces the portable variants; these just make them addressable.
The per-module flakes couldn't build standalone, so a release repo couldn't build them as separate modules (its CI runs `nix build .#lgx-portable` per module_path): - modules/amm links amm_ffi, a Cargo workspace member (it path-depends on amm_core / token_core / twap_oracle_core), so it can only be built with the whole workspace as source. - apps/amm depends on the amm_module core module, which only the root flake injected. Wire them up: modules/amm pulls amm_ffi from the repo-root flake (path:../..) via externalLibInputs; apps/amm pulls amm_module from the sibling flake (path:../../modules/amm) with inputs.lez_core.follows so the UI and core share one wallet, and adopts the root flake's Basecamp-safe Logos.Wallet staging (the qmldir directive stripping the standalone postInstall was missing). Both now build `.#lgx-portable` on their own — verified end to end. The repo-root flake is unaffected: it builds src = ./modules/amm / ./apps/amm with its own inputs and ignores these subdir flakes.
gravityblast
approved these changes
Sep 2, 2026
On a fresh wallet home the CLI runs a first-run setup before the subcommand: it reads
a password (Input password:), auto-generates a throwaway wallet, then runs
restore-keys, which reads the recovery phrase and its own password. So a fresh home
consumes three stdin lines — setup-password, recovery-phrase, restore-password — not
two. restore_test_wallet fed only two (mnemonic, password), so on a fresh home the
mnemonic was eaten as the setup password and "test" became the phrase ("word count:
1"). An already-initialised home skips the setup read, which is why re-running a
failed bootstrap appeared to work.
Rename the lez_core ref from fix/generic-tx-instruction-bstr to byte-string-fix — the same upstream commit (b60be46; the branch was renamed), so the locked rev is unchanged. Staying on this branch is deliberate: main's transitive logos-execution-zone (the wallet-ffi) has moved ahead of the deployed sequencer and the local v0.2.4 wallet/spel CLI, so its wallet-storage/config formats no longer match — the app opens but can't load a wallet the v0.2.4 CLI wrote. Document that coupling in the flake comment. Updates the four flakes (root + modules/amm + modules/stablecoin + apps/amm) and their locks.
0x-r4bbit
force-pushed
the
chore/release-packaging
branch
from
September 2, 2026 14:42
6a70575 to
287d210
Compare
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.
No description provided.