Skip to content

K2GO-414 chore(binaries): bump native binaries to binaries-2026-09-23_22-33 - #583

Merged
luisguzman-adfa merged 1 commit into
mainfrom
chore/K2GO-414-bump-native-binaries
Sep 24, 2026
Merged

luisguzman-adfa merged 1 commit into
mainfrom
chore/K2GO-414-bump-native-binaries

Conversation

@luisguzman-adfa

Copy link
Copy Markdown
Collaborator

What

Bump the pinned native binaries from binaries-2026-09-01_11-20 to
binaries-2026-09-23_22-33.

  • controller/binary_version.txt: the release tag.
  • controller/app/src/main/assets/ninja_manifest.json: the SHA256 audit hashes.

cacert.pem did not change, so it is not touched. The .so files are gitignored
and are fetched at build time by :app:syncNativeArtifacts.

Why

binaries-2026-09-23_22-33 comes from a main run. It carries the futex_time64
fix (K2GO-411) and the rsync IDN fix (K2GO-414). This build lets 32-bit devices
run the Go based roles (for example Forgejo, K2GO-212).

Verification

The binary-bump-consistency check requires binary_version.txt and
ninja_manifest.json to move together. Both are in this PR. The manifest hashes
come from the release asset for this tag.

…_22-33

Pin the native binaries to the build from the main run. It carries the futex_time64 fix (K2GO-411) and the rsync IDN fix (K2GO-414). This lets 32-bit devices run the Go based roles.

binary_version.txt (the tag) and ninja_manifest.json (the SHA256 audit hashes) are bumped together, as the consistency check requires. cacert.pem did not change. The .so files are gitignored; :app:syncNativeArtifacts fetches them.
@luisguzman-adfa
luisguzman-adfa merged commit 1e86d81 into main Sep 24, 2026
4 checks passed
@luisguzman-adfa
luisguzman-adfa deleted the chore/K2GO-414-bump-native-binaries branch September 24, 2026 10:24
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.

1 participant