Skip to content

Fix qlrd release pr - #28

Merged
qlrd merged 3 commits into
qlrd:chore/releasefrom
joaozinhom:fix_qlrd_release_pr
Aug 4, 2026
Merged

qlrd merged 3 commits into
qlrd:chore/releasefrom
joaozinhom:fix_qlrd_release_pr

Conversation

@joaozinhom

Copy link
Copy Markdown

important to mentions the claude helps me with some tricks and with the all the test coverage

qlrd and others added 3 commits August 4, 2026 10:34
This commit updates application to it's internet-less installer, i.e,
for now every installation will download upstream from latest release,
i.e., v26.08.0 to be released.

Another third step added was the reproductibility hashes on github
actions's logs, so an interested user could compare his/her own krux
firmware build with those downloaded, hashed, verified and embeeded on
CI.

It's expected that the first build of this commit will fail and the
previous commit (4216e0aa) isn't the final one and this should be tagged
after firwmare release, so it will download the correct firmware (and
thus show to users correct reproductibility hashes).

It's expected that the subsequent builds (starting from a3fac76) build
with success accompained with same firmware hashes produced by `uv run
python reproductibility.py` on `selfcustody/krux` repo.

For purposes of verification, every rebase should be accompained with
his commit hashes for `git` inspection.

- 4216e0aa
- a3fac76
@joaozinhom
joaozinhom marked this pull request as draft August 4, 2026 19:04
@qlrd
qlrd marked this pull request as ready for review August 4, 2026 19:17
@qlrd
qlrd merged commit abf7a51 into qlrd:chore/release Aug 4, 2026
1 check passed
qlrd added a commit that referenced this pull request Aug 4, 2026
This commit updates application to it's internet-less installer, i.e,
for now every installation will download upstream from latest release,
i.e., v26.08.0 to be released.

Another third step added was the reproductibility hashes on github
actions's logs, so an interested user could compare his/her own krux
firmware build with those downloaded, hashed, verified and embeeded on
CI.

It's expected that the first build of this commit will fail and the
previous commit (4216e0aa) isn't the final one and this should be tagged
after firwmare release, so it will download the correct firmware (and
thus show to users correct reproductibility hashes).

It's expected that the subsequent builds (starting from a3fac76) build
with success accompained with same firmware hashes produced by `uv run
python reproductibility.py` on `selfcustody/krux` repo.

For purposes of verification, every rebase should be accompained with
his commit hashes for `git` inspection.

- 4216e0aa
- a3fac76
- e6c00af (co-authored by @joazinhom on
#27)
- abf7a51 (co-authored by @joazinhom on
#28)

Co-authored-by: joaozinhom <joaomcr@proton.me>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants