SeedSigner

This commit changes how the SeedSigner software figures out its own version number when it cannot read version info from the local git repository. Instead of immediately giving up, it now checks whether it is running inside GitHub Actions and, if so, uses environment variables provided by GitHub to determine the version. There is no security issue visible in this change.

This commit removes a hard-coded version number from the SeedSigner software and instead reads the version from a generated file or git metadata. It also adds a debug print statement that exposes the device's hostname setting to standard output. There is no direct security vulnerability in the diff itself, but the change makes version reporting depend on build-time files and local git state, and it leaks an internal configuration value in logs or console output.

This commit is a small code-quality improvement that cleans up how a file path is constructed. It uses a standard function (os.path.normpath) to remove redundant '..' segments from a path and prints the actual resolved path instead of a hardcoded string. There is no direct evidence this fixes an exploitable security vulnerability.

This commit only changes test files. It removes direct assignments to a shared Settings.HOSTNAME variable inside tests and replaces one with a temporary mock. This prevents test runs from accidentally leaving the simulated device hostname in an unexpected state for later tests. There is no change to the actual SeedSigner application or its security behavior.

This commit adds a helper that can write the project's version number and last source-edit time into a small JSON file. It is a build/infrastructure change with no apparent security relevance.

This commit is a small code cleanup in SeedSigner's version helper. It extracts a repeated file-path calculation into a shared method and updates a comment about where the version file is written. There is no security-relevant change: the same file is read/written, the same JSON parsing occurs, and no new inputs or trust decisions are introduced.

This commit simply moves existing version-checking code from one file to a new dedicated helper file. It is a routine code cleanup with no visible security implications.

This is a test-only cleanup. A developer fixed a unit test so that a fake version of `os.walk` is only active inside the test that needs it, instead of accidentally staying in place for later tests. It does not change any production code or affect real users.

This commit is a small code cleanup that changes how the app finds the project root directory. It replaces a method based on the current working directory with one based on the location of the source file itself. There is no security issue visible in the change.

This commit adds a new test file to fix a test-suite quirk where tests passed when run individually but failed when run with the root `pytest` command. It is purely a testing/development change and does not alter any production code or security behavior.

This commit changes how the app finds its own source-code folder so it works correctly in automated build environments. The old code assumed the project path always contained the literal text '/src' and used string splitting, which could fail or behave unexpectedly on some systems. The new code walks up a fixed number of parent directories. There is no direct security vulnerability here, but the old approach could have produced wrong paths in unusual environments.

This commit fixes a minor test-only bug. The test file was calling a unittest method (self.skipTest) inside a pytest-based test, which does not work correctly. The change replaces it with pytest.skip and adjusts imports. It only affects how one test is skipped when there is no Git directory; it does not change any production code or security behavior.

This is a one-line tightening of a string comparison. The code previously accepted a tag file's commit hash if it merely began with the same characters as the git reference; now it requires an exact match. This prevents a partial-prefix match from being treated as a valid tag, which could in theory cause the wrong software version tag to be displayed or selected. There is no direct evidence this is exploitable for harm, and the commit message does not describe it as a security fix.

This commit only changes how a settings menu screenshot is generated for documentation. It adds a way to pre-select a specific menu button so the screenshot can show the bottom of the settings list. There is no security-relevant change to user-facing behavior, cryptography, or private data handling.

This commit is a minor cleanup and improvement to how the app displays its own version information. It makes the version label match an official git tag when one exists, and it tidies up a routine that checks when source files were last edited. There is no security-relevant change here.

This commit adds a new 'Version' menu in Settings and updates the opening splash screen to show the software version. It is a straightforward user-interface feature with no security relevance.

This commit is a routine UI enhancement for a Bitcoin hardware wallet project. It renames an internal method, adds a helper that finds the most recently modified source file, and displays that timestamp on the version/about screen. There is no security-relevant change.

This commit only rewrites code comments and removes an early-return check that previously skipped git detection when running on the SeedSigner OS. The actual behavior of the version detection function is unchanged for the normal case, and no security-sensitive code is modified.

This commit fixes a test-code-only cleanup issue. Some tests were directly changing a shared Settings.HOSTNAME value and leaving it changed for later tests, which could make later tests behave incorrectly. The patch removes those direct assignments in two test files and replaces one with a temporary mock that automatically restores the original value. There is no change to the actual SeedSigner application code that users run, so this does not affect real devices or user security.

This is a one-line correction in a test file. The test was checking that a 'passphrase' setting was NOT included in parsed QR-code settings, but the intended behavior is that it SHOULD be included. The change fixes the test assertion to match the actual expected behavior. It does not change any production code and has no direct security impact on users.

This commit only changes a test file. It adds one more unrecognized setting ('passphrase=E') to an existing test that checks the SettingsQR parser ignores unknown settings. There is no change to production code, no security fix, and no vulnerability introduced.

This is a test-only cleanup. A unit test was replacing the `os.walk` function with a fake version and not restoring it afterward, which could cause unrelated later tests to see the fake directory listing. The fix uses Python's `patch` helper that automatically undoes the change after the test. There is no effect on the actual SeedSigner application or its users.

This commit only updates test files to remove references to an obsolete 'xpub_export' setting. It does not change any production code, user-facing behavior, or security controls. There is no security issue in this patch.

This commit removes a user-facing setting that let advanced users disable the 'Export xpub' button. After the change, the Export xpub option is always shown in the seed options menu. This is a feature simplification, not a fix for a code vulnerability. It slightly reduces user-configurable privacy controls because a user can no longer hide the xpub export entry point, but it does not introduce a new exploit or change how xpub export actually works.

This commit only renames internal test variables and settings strings from 'coord' to 'xpub_qr'. It is a cleanup change with no effect on the actual wallet software users run, and no security relevance.