Skip to content

feat: b10x-harness in the catalog, prebuilt by target; release 0.14.8 - #28

Merged
b10x-bot[bot] merged 1 commit into
mainfrom
feat/harness-catalog
Sep 25, 2026
Merged

b10x-bot[bot] merged 1 commit into
mainfrom
feat/harness-catalog

Conversation

@b10x-bot

@b10x-bot b10x-bot Bot commented Sep 25, 2026

Copy link
Copy Markdown
Contributor

Adds b10x-harness (Linux only) as an optional aep binary; b10x now chooses a prebuilt archive only when the release has one for this machine target; b10x install follows the same default. See CHANGELOG 0.14.8. task check: 89 tests passed.

- catalog.json: b10x-harness is an optional binary of aep (archive and
  cargo from beyond10x/harness). A new `platforms` field limits it to
  Linux; b10x does not plan it elsewhere.
- resolve.rs reads the targets each newest release's SHA256SUMS lists
  (install::listed_targets); plan.rs chooses prebuilt only when this
  machine's target is among them, else cargo, else a warning naming
  the target. The per-repository yes/no flag is gone.
- b10x install <cli> uses the same default; since 0.14.7 it still chose
  cargo whenever cargo was on PATH.
- aep:init: metaharness is optional and installed with b10x install.
- Docs name b10x-harness; tests cover target selection, SHA256SUMS
  parsing and the platform rule. task check: 89 tests passed.
- Checked: b10x install b10x-harness / metaharness on x86_64 Linux
  install 0.13.2 and 0.8.0 from their prebuilt archives.
@b10x-bot
b10x-bot Bot merged commit 17ccede into main Sep 25, 2026
6 checks passed
@b10x-bot
b10x-bot Bot deleted the feat/harness-catalog branch September 25, 2026 20:58
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.

0 participants