Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps androidx.navigation:navigation-compose from 2.10.0 to 2.10.1.

---
updated-dependencies:
- dependency-name: androidx.navigation:navigation-compose
  dependency-version: 2.10.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

Vault spawns plugins with VAULT_PLUGIN_MLOCK_ENABLED=true, and the SDK calls
mlockall before the go-plugin handshake. The plugin binary has no
cap_ipc_lock (setcap does not survive the bind mount) and runs as uid 100,
so it is bounded by RLIMIT_MEMLOCK. Docker Desktop defaults that to
unlimited; dockerd on the GitHub Ubuntu runner defaults to 8 MiB, which the
~15 MB static binary exceeds. The plugin exited with "cannot allocate
memory" and Vault reported only the generic "not compiled for this
architecture" error, even though the log showed EM_X86_64 on amd64.

Set ulimits.memlock: -1 on the vault service. No-op on Docker Desktop,
fixes the Initialize Vault step on CI.

`docker build` without `--platform` produces a binary for the Docker daemon's
default platform, which only coincidentally matched the Vault container on a
dev machine: both followed the host architecture. On CI the two are chosen
independently, and a plugin binary built for a different architecture than the
Vault container dies before the go-plugin handshake, leaving only Vault's
opaque "Failed to read any lines from plugin's stdout" behind a 400 on mount.

Resolve the build platform from the Vault image itself so the binary and the
container that execs it always agree.

The logs endpoint sets SkipInnerTransactionConversion, so inner
transactions are returned as their own rows and TxnRow.RootTxn is nil.
TxnRow.Next still built the token from Extra.RootIntra and, when
ascending, added countInner(tr.Txn). Stored inner rows have their nested
inner transactions stripped, so the count was 0 and the token pointed at
the root transaction's intra. The next request selected the same inner
transaction again and produced the same token: on the last page this
repeated forever, on earlier pages it duplicated the last entry.

Next now returns the row's own intra for an inner transaction returned
without its root.

The logs endpoint sets SkipInnerTransactionConversion, so inner
transactions are returned as their own rows and TxnRow.RootTxn is nil.
TxnRow.Next still built the token from Extra.RootIntra and, when
ascending, added countInner(tr.Txn). Stored inner rows have their nested
inner transactions stripped, so the count was 0 and the token pointed at
the root transaction's intra. The next request selected the same inner
transaction again and produced the same token: on the last page this
repeated forever, on earlier pages it duplicated the last entry.

Next now returns the row's own intra for an inner transaction returned
without its root.

Vault spawns plugins with VAULT_PLUGIN_MLOCK_ENABLED=true, and the SDK calls
mlockall before the go-plugin handshake. The plugin binary has no
cap_ipc_lock (setcap does not survive the bind mount) and runs as uid 100,
so it is bounded by RLIMIT_MEMLOCK. Docker Desktop defaults that to
unlimited; dockerd on the GitHub Ubuntu runner defaults to 8 MiB, which the
~15 MB static binary exceeds. The plugin exited with "cannot allocate
memory" and Vault reported only the generic "not compiled for this
architecture" error, even though the log showed EM_X86_64 on amd64.

Set ulimits.memlock: -1 on the vault service. No-op on Docker Desktop,
fixes the Initialize Vault step on CI.

Paths: docker-compose.yml

## [2.5.0-beta.2](https://github.com/algorandfoundation/algokit-lora/compare/v2.5.0-beta.1...v2.5.0-beta.2) (2026-09-14)

### 🚀 Features

* add 'lease' field to the transaction wizard ([b860e4a](https://github.com/algorandfoundation/algokit-lora/commit/b860e4a23a355e889484f621d55604a5e0f6d029))