This commit syncs the stable release version back to main branch
to ensure the next beta cycle starts from the correct version base.

Release: 2.4.1
Tag: v2.4.1

## [2.4.1](https://github.com/algorandfoundation/algokit-lora/compare/v2.4.0...v2.4.1) (2026-09-10)

### 🐛 Bug Fixes

* use utils 9.2.2 to work with Pera's PQ fee changes ([#609](https://github.com/algorandfoundation/algokit-lora/issues/609)) ([7461262](https://github.com/algorandfoundation/algokit-lora/commit/746126278c85c16b1da5c8570e0e156aafb24de4))

This promotion merges tested changes from main branch to release for production release.

The comment claimed the generator was "pinned in go.mod" while the
recipe ran oapi-codegen@v2.4.1 against a go.mod requiring v2.8.0. `go
run pkg@version` ignores the module's requirements entirely, so the two
were free to drift, and had: the next `go get -u` would bump the library
the generated code is compiled against while `make generate` kept
emitting v2.4.1 output.

The version now comes from `go list -m`, so the claim holds by
construction and a library bump carries the generator with it. Left as
`go run pkg@version` rather than a go.mod `tool` directive on purpose:
the directive pulls the generator's own dependency graph into this
module, which cost twelve indirect requirements and a bump to
rogpeppe/go-internal for a tool nothing in the build imports.

Recursively expanded, so the query runs for `make generate` and not for
`make build` or `make test`, and guarded so an unresolvable version says
so rather than running `oapi-codegen@`.

Note that api/lf.go is still v2.4.1 output, so the next `make generate`
will carry a generator bump alongside whatever the spec changed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RrRQEXGWtmBskmUbiZbRi1

Bumps the all group with 9 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@algorandfoundation/tealscript](https://github.com/algorandfoundation/TEALScript) | `0.106.3` | `0.107.2` |
| [@tsconfig/node22](https://github.com/tsconfig/bases/tree/HEAD/bases) | `22.0.5` | `22.0.6` |
| [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/eslint-plugin) | `8.64.0` | `8.69.0` |
| [prettier](https://github.com/prettier/prettier) | `3.9.5` | `3.9.6` |
| [rolldown](https://github.com/rolldown/rolldown/tree/HEAD/packages/rolldown) | `1.2.0` | `1.2.7` |
| [semantic-release](https://github.com/semantic-release/semantic-release) | `25.0.7` | `25.0.9` |
| [tsx](https://github.com/privatenumber/tsx) | `4.23.1` | `4.23.13` |
| [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/typescript-eslint) | `8.64.0` | `8.69.0` |
| [uuid](https://github.com/uuidjs/uuid) | `14.0.1` | `14.0.2` |



Updates `@algorandfoundation/tealscript` from 0.106.3 to 0.107.2
- [Release notes](https://github.com/algorandfoundation/TEALScript/releases)
- [Commits](https://github.com/algorandfoundation/TEALScript/compare/0.106.3...0.107.2)

Updates `@tsconfig/node22` from 22.0.5 to 22.0.6
- [Commits](https://github.com/tsconfig/bases/commits/HEAD/bases)

Updates `@typescript-eslint/eslint-plugin` from 8.64.0 to 8.69.0
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.69.0/packages/eslint-plugin)

Updates `prettier` from 3.9.5 to 3.9.6
- [Release notes](https://github.com/prettier/prettier/releases)
- [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md)
- [Commits](https://github.com/prettier/prettier/compare/3.9.5...3.9.6)

Updates `rolldown` from 1.2.0 to 1.2.7
- [Release notes](https://github.com/rolldown/rolldown/releases)
- [Changelog](https://github.com/rolldown/rolldown/blob/main/CHANGELOG.md)
- [Commits](https://github.com/rolldown/rolldown/commits/v1.2.7/packages/rolldown)

Updates `semantic-release` from 25.0.7 to 25.0.9
- [Release notes](https://github.com/semantic-release/semantic-release/releases)
- [Commits](https://github.com/semantic-release/semantic-release/compare/v25.0.7...v25.0.9)

Updates `tsx` from 4.23.1 to 4.23.13
- [Release notes](https://github.com/privatenumber/tsx/releases)
- [Changelog](https://github.com/privatenumber/tsx/blob/master/release.config.cjs)
- [Commits](https://github.com/privatenumber/tsx/compare/v4.23.1...v4.23.13)

Updates `typescript-eslint` from 8.64.0 to 8.69.0
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/typescript-eslint/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.69.0/packages/typescript-eslint)

Updates `uuid` from 14.0.1 to 14.0.2
- [Release notes](https://github.com/uuidjs/uuid/releases)
- [Changelog](https://github.com/uuidjs/uuid/blob/main/CHANGELOG.md)
- [Commits](https://github.com/uuidjs/uuid/compare/v14.0.1...v14.0.2)

---
updated-dependencies:
- dependency-name: "@algorandfoundation/tealscript"
  dependency-version: 0.107.2
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all
- dependency-name: "@tsconfig/node22"
  dependency-version: 22.0.6
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: all
- dependency-name: "@typescript-eslint/eslint-plugin"
  dependency-version: 8.69.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all
- dependency-name: prettier
  dependency-version: 3.9.6
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: all
- dependency-name: rolldown
  dependency-version: 1.2.7
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: all
- dependency-name: semantic-release
  dependency-version: 25.0.9
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: all
- dependency-name: tsx
  dependency-version: 4.23.13
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: all
- dependency-name: typescript-eslint
  dependency-version: 8.69.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: all
- dependency-name: uuid
  dependency-version: 14.0.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: all
...

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

Runs `nodekit logs` against a real node on both runners, before and
after a stop, and adds internal/algod/logs to the paths that trigger the
workflow.

Two things the obvious version of this would have got wrong. `sudo`
resets the environment, so GOCOVERDIR would not reach the privileged
runs and they would contribute nothing to the coverage profile the last
step collects; `sudo -E` carries it through. And guarding the
unprivileged read with `|| echo` swallows every non-zero exit, panic
included, which is precisely the failure it was meant to catch: only the
message separates the two, so the message is what is asserted on.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RrRQEXGWtmBskmUbiZbRi1

Reading a node's logs required knowing that algod writes a logrus JSON
file, where config.json puts it, and reaching for `tail -f | jq`. This
makes it a first-class operation.

`nodekit logs` shows warnings and errors by default, with --all, --level,
--since, --filter, --lines, --follow, --json and --file. --lines counts
matching entries rather than raw lines, which is what makes the default
invocation useful on a log that is ~99% info. The rotated archives are
read as part of one history, decompressed on the way past.

The reader lives in internal/algod/logs and is independent of the CLI.
A request for a fixed number of entries walks backwards from the end of
the newest source under a 512 MiB budget; a request for every match
streams forwards from the oldest, holding nothing (a million entries at
58 MiB of RSS on a 692 MiB log, against 4.7 GiB buffered). A prescreen
decides the great majority of lines from their raw bytes, at ~10x the
throughput of parsing each one, and is fuzz-guarded against ever
rejecting a line the full filter would keep.

config.Config gains LogPaths, mirroring go-algorand's ResolveLogPaths so
that HotDataDir, LogFileDir and LogArchiveDir are honoured rather than
assuming <datadir>/node.log.

Two fixes fall out of this. IsDataDir treated only os.IsNotExist as a
missing directory, so a permission error dereferenced a nil FileInfo;
and a command that returned an error printed nothing and still exited 0,
which made every failure invisible to a shell script. main now reports
the error on stderr and exits non-zero, and cobra is silenced so it is
not printed twice. The upgrade notice moves to stderr for the same
reason: it must not land in the middle of a piped stream.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RrRQEXGWtmBskmUbiZbRi1

## [2.4.1-beta.2](https://github.com/algorandfoundation/algokit-lora/compare/v2.4.1-beta.1...v2.4.1-beta.2) (2026-09-10)

chore: bump algokit-subscriber to 3.3.0 and resolve npm audit vulns