Skylight Wallet

This commit updates precompiled Monero wallet library files and the matching Dart package reference in a dependency lock file. The actual source code changes are not visible because the libraries are binary files. There is no information in the commit message or supplied references indicating this update fixes or introduces any security issue.

This commit changes how users restore a Monero wallet in the Skylight Wallet app. It makes the 'restore height' field optional, automatically fills it for newer Polyseed seeds, and adds support for restoring from BIP39-style mnemonic phrases (common 12/24-word seeds). The changes are mostly usability improvements, but they touch sensitive wallet-recovery code and introduce new dependencies for seed handling. There is no direct evidence in the commit of a security vulnerability, but the new BIP39 conversion logic and the changed restore flow deserve careful review because mistakes here could lead to users restoring the wrong wallet or leaking keys.

This commit updates pre-built Monero library files and the version of a related Dart package, but provides no description of why the update was made. The actual code inside the updated libraries is not shown, so we cannot tell from this commit alone whether it fixes a security issue, adds a feature, or is just routine maintenance.

This commit changes how a cryptocurrency wallet app refreshes its data. Previously, three refresh operations ran at the same time in separate background workers. Now they run one after another. The commit message simply says 'Call refresh methods properly.' There is no explicit security explanation in the commit or supplied references, so any security relevance is speculative. The change likely fixes a race condition or crash caused by concurrent access to the same wallet memory, which could in turn prevent inconsistent wallet state or denial-of-service for the user.

This commit fixes a bug where restoring an older-style cryptocurrency wallet seed would fail. The app now also accepts a specific temporary 'No response from HTTP server' state from the underlying wallet library as a valid signal to proceed with the restore. It also removes an unused import in a seed-generation screen. There is no direct evidence this is a security vulnerability; it appears to be a reliability/bug-fix change.

This commit speeds up the wallet creation screen by fetching the blockchain height ahead of time and by running some setup steps in the background instead of waiting for each one to finish. The changes are framed as a performance optimization. There is no direct evidence in the commit that this fixes a security vulnerability, but it does change how sensitive wallet setup tasks are sequenced and how a shared cache is accessed.

This commit changes a single dependency version in a Dart package file from a flexible version range (^0.20.2) to an exact pinned version (0.20.2). This is a routine build/dependency management change with no visible security relevance in the commit itself or supplied references.

This commit locks down the exact versions of software building blocks used by the Skylight Wallet app and its Docker build image. It upgrades Flutter from 3.27.1 to 3.38.3, pins the Dart SDK to 3.10.1, and replaces flexible version ranges (like ^1.0.8) with exact versions in the project's dependency list. It also refreshes the lock file with newer patch/minor versions of many supporting libraries. The change is primarily a supply-chain hygiene improvement: it makes builds more reproducible and prevents unexpected future updates, but it also pulls in newer library versions that may contain routine bug and security fixes.

This commit adds an automated GitHub Actions release pipeline for a wallet app. It builds Android and Linux packages, signs them with GPG and Android release keys, and publishes them on GitHub Releases. There is no direct evidence of a security vulnerability in the code changes themselves, but the pipeline handles sensitive secrets and includes a prebuilt binary library that changed without source diff visibility.

This commit is a minor user-interface polish change. It stops a navigation button from doing anything if the user is already on the page it would open. There is no security relevance in the commit message or code change.

This commit replaces a Linux shared library file (monero_libwallet2_api_c.so) with a new version to fix a loading problem on Linux. The actual source code changes are not visible because the file is a compiled binary. There is no evidence in the commit message or diff that this change is security-related.

This commit only changes the application's version number from 1.0.1+5 to 1.0.2+6 in a configuration file. There are no code changes, no security fixes, and no functional changes visible in this patch.

This commit simply reduces noisy logging. It removes two routine debug messages that were printed every time the wallet checked its connection, and adds one cleaner message only when the connection status actually changes. There is no security fix here.

This commit adds a precompiled binary library file for 32-bit ARM Android devices (armeabi-v7a). It is a build/packaging change with no source code modifications visible in the diff. There is no evidence in the commit or supplied references that this change fixes or introduces a security vulnerability.

This commit updates pre-built Monero wallet library files, fixes leftover Git merge-conflict markers in the app's startup code, and limits a custom certificate-file workaround to Android only. The merge-conflict cleanup is a routine code tidying change. The certificate change means non-Android platforms will now rely on normal system certificate verification instead of a bundled certificate file, which is generally a good thing but could affect connection behavior. The library updates are opaque binary changes whose security implications cannot be judged from the diff alone.

This commit only changes two user-visible warning messages in the app's translation files. In English and Portuguese, the warning about running out of subaddresses now says 'used address' instead of 'used subaddress'. There is no code, security logic, or behavior change.

This commit fixes a bug in a cryptocurrency wallet app where a warning about reaching the maximum number of subaddresses (separate receiving addresses) could appear at the wrong time or with wrong data. The changes remove a condition that only saved wallet state after transactions were loaded, and they stop assuming a default value of 1 when the saved subaddress index is missing. The security relevance is indirect: it mainly prevents user confusion and possible app misbehavior, not a direct theft or remote attack.

This commit fixes the filename of the built AppImage package. The build tool was producing a file named like 'Skylight_Wallet-...' but the script later looked for 'skylight-wallet-...' (lowercase), so the final output message and any downstream steps could not find the file. The patch renames the generated file to the expected lowercase name and adds a clear error if it is missing. There is no security relevance.

This commit adds a new Linux AppImage build script and packaging files for the Skylight Wallet application, plus a window icon and minor dependency updates. There is no security-relevant code change and no indication of a vulnerability being fixed.

This commit only changes the app's build number in the package configuration file (from version 1.0.1 to 1.0.1+5). It does not modify any code, dependencies, permissions, or security settings. There is no security relevance.

This commit only changes the application's version number in a configuration file (from 1.0.0+4 to 1.0.1). There are no code changes, no security fixes, and no functional changes visible in the diff.