Skip to content

Releases

0.9.0 - 2026-11-19

Choose a tag to compare

@github-actions github-actions released this 19 Nov 17:11
Immutable release. Only release title and notes can be modified.
v0.9.0
01eca87

Release Notes

Added

  • eb-stack stack buildenv --build-list LIST [--installed MODULES] names every toolchain a build list builds with and whether its buildenv/default-<toolchain> module is installed, listed or missing, with the easyconfig that adds it. --strict exits 1 while one is missing, so a pipeline can require a build environment for every toolchain it ships.

Changed

  • A release is cut with cog bump: cog.toml runs tools/release-prepare, which builds the changelog, sets the version in every file that declares or states it, and regenerates llms.txt and llms-full.txt. It refuses when a listed file no longer names the old version.

Install eb_stack 0.9.0

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/stackhands/eb-stack/releases/download/v0.9.0/eb_stack-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://github.com/stackhands/eb-stack/releases/download/v0.9.0/eb_stack-installer.ps1 | iex"

Download eb_stack 0.9.0

File Platform Checksum
eb_stack-aarch64-apple-darwin.tar.xz Apple Silicon macOS checksum
eb_stack-x86_64-apple-darwin.tar.xz Intel macOS checksum
eb_stack-x86_64-pc-windows-msvc.zip x64 Windows checksum
eb_stack-aarch64-unknown-linux-gnu.tar.xz ARM64 Linux checksum
eb_stack-x86_64-unknown-linux-gnu.tar.xz x64 Linux checksum
eb_stack-x86_64-unknown-linux-musl.tar.xz x64 MUSL Linux checksum

0.8.0 - 2026-11-18

Choose a tag to compare

@github-actions github-actions released this 18 Nov 12:28
Immutable release. Only release title and notes can be modified.
v0.8.0
0cb3565

Release Notes

Added

  • ledger backfill, ledger anchor, ledger verify-anchors and ledger project maintain a ledger in process. backfill appends a finding record for each observation of a manifest pinned by its SHA-256, at the observation time, and a rerun appends nothing. anchor signs the day's head and publishes it once as ANCHORS/YYYY-MM-DD.head.json after verify proves it binds to the log and extends the latest anchor; verify-anchors proves the chain. project writes index.json, index.md and per-package JSON and Markdown history from a log whose signed head covers every record. Each prints one JSON object and exits 2 when refused; backfill and anchor exit 75 when an append or a signature did not finish. Each has an MCP tool: eb_ledger_backfill, eb_ledger_anchor, eb_ledger_verify_anchors and eb_ledger_project.

Fixed

  • A from-commit read uses a directory it created for that read. It no longer shares eb-stack-from-commit-<pid> with every other read in the process, and it does not remove a directory that was already there.
  • A failed verification command is a sanity finding, or timeout, unless its output names a transport, executor, runtime, or resource cause, so an Lmod error: line no longer makes it compile. Finding summaries and campaign history name the class and exit status as the state file does, sanity and exit 1, not Sanity and exit Some(1).
  • A generated stack policy is a new file for each solve. The MCP server no longer reuses eb-stack-policy-<toolchain>-<pid>.json, and it removes the file when the solve returns.
  • A job stack admit refuses for want of inodes carries a refusal: the inodes it is short, then the available, reserved, footprint and margin that decided it. It was null, so only a failed quota or scheduler command said why.
  • A lock's timestamp is SOURCE_DATE_EPOCH when that variable is a number of seconds. Two solves of the same inputs then write the same time.
  • A pin on a package the trees have only outside the solve's toolchain hierarchy, in a stack solve policy or a package plan / package bump stack policy, now fails with the hierarchy searched and the toolchains the trees have the package on, instead of "unknown package" and "names a package with no candidate at all". A stack-policy exclusion gets the same message.
  • A step of the Cargo prelude that fails stops EasyBuild's install command again: the host triple is read inside the prelude's && chain, not after _triple="";, whose semicolon ended the chain. A missing or failing rustc still leaves the triple empty, even under pipefail.
  • A verification command runs with the module tree of the attempt's install path, <installpath>/modules/all by default, first on MODULEPATH and on EESSI_EXTRA_MODULEPATH, so module load {module} finds the module the attempt built, also after the EESSI init replaces MODULEPATH.
  • Compatible-release, caret, and tilde requirements exclude a pre-release of the next series. 1.3.0rc1 is outside ~=1.2.0 and ~1.2.3, and 2.0.0rc1 is outside ^1.2.0.
  • Date versions such as LAMMPS's 29Aug2024 compare by year, month and day, and a following _updateN by its number, so stack gap names a LAMMPS 22Jul2025_update4 recipe as the newest outside the generation instead of 29Aug2024. Requirements such as >=29Aug2024 compare the same way.
  • The CI smoke step on the eOn core fixture checks eOn-2.17.10-foss-2026.1.eb, the recipe the fixture holds, and passes only when recipe check fails on the stack dependencies the drafts leave out, with the drafts supplying quill, readcon-core and rgpot. It named the 2.17.2 recipe the fixture no longer has, so it passed on "No such file or directory" without checking anything. tests/eon_core_rgpot.rs runs the step as CI runs it.
  • The package plan residuals for an inferred moduleclass and for a dropped build requirement, and the source finding for a tree that declares no version, read as one sentence instead of carrying a run of spaces where the source line was wrapped.
  • The cargo-on-EESSI prelude quotes CC and LIBRARY_PATH. CC='gcc; echo pwned' is stored as the linker, and it is not run.
  • The import scan of a PyPI source tree skips standard-library modules, test suites, documentation, examples and maintainer scripts, and reads only import statements outside triple-quoted strings, so natsort 8.4.0 has 3 undeclared-import residuals instead of 29. An import whose name is part of one already reported, such as requests after requests_cache, is still reported.
  • Cargo.lock pins rustls 0.23.46 and rustix 1.1.6, the patched releases for RUSTSEC-2026-0285, RUSTSEC-2026-0346, RUSTSEC-2026-0348, RUSTSEC-2026-0349, and RUSTSEC-2026-0486.
  • component-reach resolves the closure over every recipe in the trees, so dependents on gfbf and gompi toolchains of the generation are in it. On easybuild-easyconfigs develop with the EESSI 2026.06 easystack, curl's closure gains 19 dependents on gfbf-2026.1 and gompi-2026.1, such as R, netCDF, HDF5 and SciPy-bundle, and 12 recipes only they pull in, such as Tk through CMake, so the counts go from review=106 no-rebuild=16 to review=133 no-rebuild=20. Requirements no recipe resolves are listed in closure_unresolved instead of being dropped.
  • easyblock-reach heads reach.toml and reach.md with a line that says only that eb-stack easyblock-reach generated the file, instead of the pr-overlap warning about a data branch that is never merged. The report is written to --out-dir, and no branch holds it.
  • ledger show prints each record's stage after action, so the started and finished records of one staged rebuild no longer print as two identical rows.
  • package bump and package plan keep a dependency's stated versionsuffix when the robot tree has a build with it that the solve can take: ('HDF5', '1.14.2', '-mpi') and ('HDF5', '1.14.2', '') no longer become the -serial build because that one ranks higher. The solve takes another suffix only when the target has no build with the stated one, as when -CUDA-12.9.1 moves to -CUDA-13.3.0 across a generation.
  • scripts/eessi-extend-eb.sh counts a present EESSI_*_INSTALL variable as set when the value is empty, matching EESSI-extend. An empty EESSI_SITE_INSTALL or EESSI_CVMFS_INSTALL stays in that mode and no longer also creates a user prefix.
  • scripts/eessi-extend-eb.sh defaults to EESSI 2026.06, takes the repository from EESSI_CVMFS_REPO, puts the compatibility layer's ld on PATH from EESSI_EPREFIX whether or not EESSI_VERSION was set, and creates a named EESSI_USER_INSTALL as well as the default one. The Cargo prelude takes the compatibility layer from EESSI_EPREFIX too.
  • scripts/eessi-extend-eb.sh still reaches EasyBuild when rustc is not on PATH, and the Cargo prelude takes a mirror's compatibility layer from EESSI_CVMFS_REPO when EESSI_EPREFIX is unset. CI runs tests/eessi_extend_eb_script.rs.
  • stack gap picks the bump source of a no-recipe row among builds of the newest version by toolchain family and generation instead of file name: a build on a toolchain family of the generation comes first, then the newest toolchain generation, so QuantumESPRESSO 7.5 is bumped from foss-2025b rather than NVHPC-25.3-CUDA-12.8.0, and a recipe on GCCcore-14.3.0 is preferred to one on GCCcore-11.3.0.
  • stack shard counts -f, EasyBuild's short form of --force, as forcing a rebuild, as it counts --force and --rebuild. A line that rebuilt an installed module with -f was planned as building nothing: the module had no weight and was in no closure, so a line that needs it could land in another shard and build while eb -f rebuilt it.
  • target doctor passes the EasyBuild probe of a target with EB_LOCAL_EESSI_EXTEND on only when --version prints This is EasyBuild. eb-local 2.4.0 has no extend mode, answered --version itself and passed; the failed check now carries a reason.

Documentation

  • The EESSI target in docs/orgmode/reference/targets.org and examples/targets/eessi-extend.toml needs eb-local 2.5.0 or later, the first release with EB_LOCAL_EESSI_EXTEND.
  • The PyPI how-to and the package-plan skill plan the pure-Python beautifulsoup4 example on GCCcore/15.2.0, where EESSI 2026.06 installs Python, Python-bundle-PyPI and BeautifulSoup, with the new examples/stacks/eessi-python-gcccore.toml policy, and the fixture robot holds the GCCcore-15.2.0 builds of Python 3.14.2 and Python-bundle-PyPI 2026.04. The numpy example stays on foss/2026.1, because SciPy-bundle is never on GCCcore.
  • The README says when EasyBuild alone is enough, and which stackhands tool calls each stack and ledger verb.
  • The --help text matches what the commands do: the top-level help names exit status 78 from stack admit; the second stack admit example reads the quota and the scheduler inside --lock with --quota-cmd and --live-jobs-cmd, instead of expanding squeue before the lock; campaign --help shows campaign run; stack generation --help maps 2026.06 to 2026.1; and stack batch --installed-modulerc says it reads a module tree as well as a .modulerc.lua file.
  • The stack shard and stack capacity help examples, the shard how-to, the capacity reference and the skills name a neutral example site, not one cluster: a zen2.list or zen4.list build list, a commit cache under $SCRATCH, the node feature local-disk, and the site's build host.
  • The docs match the code again: AGENTS.md lists package latest and stack capacity; the cli.org MCP list names eb_stack_footprints and eb_stack_admit; docs/campaign-boundary.md cites the current src/campaign.rs and src/foreign.rs lines and the run_target calls; the shard how-to says to plan with EESSI-extend's EASYBUILD_FILTER_DEPS, or pass that list as --filter-deps; the PyPI and CRAN ho...
Read more

0.7.4 - 2026-11-13

Choose a tag to compare

@github-actions github-actions released this 13 Nov 13:34
v0.7.4
f380e79

Release Notes

Added

  • stack capacity reads a captured scheduler snapshot and reports, per node and
    for an exact request, the eligible nodes, the nodes that can fit it and the
    free fitting slots; missing data stays unknown. The same advice is available
    through MCP.
  • stack shard takes an optional storage policy and attaches storage advice to
    every build phase: phases that fit the shared inode budget keep shared
    scratch, the rest go to node-local disk where the captured capacity allows.
    Footprint tables can mark packages that need a real disk.
  • The MCP server is described for the MCP Registry as
    io.github.stackhands/eb-stack, and a workflow publishes it with GitHub
    Actions OIDC.

Fixed

  • Materialized execution lists are bound to their exact bytes, and phase advice
    to the generated list.
  • Opaque shard roots keep their disk requirements.
  • GPU slot division is checked, and CPU advice survives unknown GPU data.
  • The footprint buffer used for estimates is the one hashed into the plan.
  • File robot roots are normalized in recipe check.

Changed

  • The repository is stackhands/eb-stack; links, docs and the SBOM tool vendor
    name the stackhands organisation.

Install eb_stack 0.7.4

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/stackhands/eb-stack/releases/download/v0.7.4/eb_stack-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://github.com/stackhands/eb-stack/releases/download/v0.7.4/eb_stack-installer.ps1 | iex"

Download eb_stack 0.7.4

File Platform Checksum
eb_stack-aarch64-apple-darwin.tar.xz Apple Silicon macOS checksum
eb_stack-x86_64-apple-darwin.tar.xz Intel macOS checksum
eb_stack-x86_64-pc-windows-msvc.zip x64 Windows checksum
eb_stack-aarch64-unknown-linux-gnu.tar.xz ARM64 Linux checksum
eb_stack-x86_64-unknown-linux-gnu.tar.xz x64 Linux checksum
eb_stack-x86_64-unknown-linux-musl.tar.xz x64 MUSL Linux checksum

0.7.3 - 2026-11-11

Choose a tag to compare

@github-actions github-actions released this 12 Nov 04:12
v0.7.3

Release Notes

Distribution

  • Static x86-64 Linux archives are published by the standard release workflow.

Fixed

  • Failed scheduler observations retain every reservation even when stale-record
    removal is requested.
  • Explicit waiting forecasts arbitrate admission under the shared lock without
    charging each other's build peaks; setup, admitted, legacy and unknown writers
    retain their reservations.
  • Explicit root module destinations govern installed-state checks, dependency
    traversal, shard weight and inode estimates without borrowing a same-named
    root from another module tree.
  • Lifted CPU roots contribute build cost only when their destination needs
    installation; requested rows remain in the emitted lists.
  • Mixed destination roots retain every dependency needed by another row's
    closure, while installed CPU and CVMFS dependencies remain reusable.
  • Plan digests include the installed state of explicitly located roots.

Install eb_stack 0.7.3

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/HaoZeke/eb-stack/releases/download/v0.7.3/eb_stack-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://github.com/HaoZeke/eb-stack/releases/download/v0.7.3/eb_stack-installer.ps1 | iex"

Download eb_stack 0.7.3

File Platform Checksum
eb_stack-aarch64-apple-darwin.tar.xz Apple Silicon macOS checksum
eb_stack-x86_64-apple-darwin.tar.xz Intel macOS checksum
eb_stack-x86_64-pc-windows-msvc.zip x64 Windows checksum
eb_stack-aarch64-unknown-linux-gnu.tar.xz ARM64 Linux checksum
eb_stack-x86_64-unknown-linux-gnu.tar.xz x64 Linux checksum
eb_stack-x86_64-unknown-linux-musl.tar.xz x64 MUSL Linux checksum

0.7.2 - 2026-11-11

Choose a tag to compare

@github-actions github-actions released this 11 Nov 23:37
v0.7.2

Release Notes

Fixed

  • Cargo checksum entries with long crate filenames use multiline dictionaries
    within the EasyBuild line limit.
  • Repeated Cargo bumps replace checksums identified by the original recipe,
    the emitted recipe and the fetched lockfile, including when the target
    recipe is present in the robot tree.
  • Recipe and module directory walks stay bounded while resolving stack inputs.

Docs

  • The manual groups installation, first commands and task-specific guides
    around the executable command surface.

Install eb_stack 0.7.2

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/HaoZeke/eb-stack/releases/download/v0.7.2/eb_stack-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://github.com/HaoZeke/eb-stack/releases/download/v0.7.2/eb_stack-installer.ps1 | iex"

Download eb_stack 0.7.2

File Platform Checksum
eb_stack-aarch64-apple-darwin.tar.xz Apple Silicon macOS checksum
eb_stack-x86_64-apple-darwin.tar.xz Intel macOS checksum
eb_stack-x86_64-pc-windows-msvc.zip x64 Windows checksum
eb_stack-aarch64-unknown-linux-gnu.tar.xz ARM64 Linux checksum
eb_stack-x86_64-unknown-linux-gnu.tar.xz x64 Linux checksum

0.7.1 - 2026-11-08

Choose a tag to compare

@github-actions github-actions released this 08 Nov 18:32
v0.7.1
477bafe

Release Notes

Changed

  • The crates.io package carries the sources, the TOML tables they include,
    the README, LICENSE, CHANGELOG and CITATION. The test corpus, fixtures,
    manual, skills, examples and delivery bundles stay in the repository;
    the 0.7.0 archive was 1589 files and 13.8 MiB, most of it tests.

Docs

  • The manual and README describe the 0.7.x GitHub release as carrying
    every command, and crates.io alone as still 0.3.0; the Org pages that
    print a version are on the release checklist; CONTRIBUTING names the
    publish command.

Install eb_stack 0.7.1

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/HaoZeke/eb-stack/releases/download/v0.7.1/eb_stack-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://github.com/HaoZeke/eb-stack/releases/download/v0.7.1/eb_stack-installer.ps1 | iex"

Download eb_stack 0.7.1

File Platform Checksum
eb_stack-aarch64-apple-darwin.tar.xz Apple Silicon macOS checksum
eb_stack-x86_64-apple-darwin.tar.xz Intel macOS checksum
eb_stack-x86_64-pc-windows-msvc.zip x64 Windows checksum
eb_stack-aarch64-unknown-linux-gnu.tar.xz ARM64 Linux checksum
eb_stack-x86_64-unknown-linux-gnu.tar.xz x64 Linux checksum

0.7.0 - 2026-11-08

Choose a tag to compare

@github-actions github-actions released this 08 Nov 16:41
v0.7.0
defb6ae

Release Notes

The behaviours the develop line carried and main lacked, ported one test
at a time (120 tests by name, all green on main now).

Added

  • package bump --foreign RECIPE (MCP foreign): a Spack package.py or
    conda-forge recipe whose dependencies the bump inspects for names the
    source .eb never declared, mapped through the package-config aliases.
  • Package config: the alias table form rejects unknown keys; empty alias
    and virtual names or values, and a patch sha256 that is not a SHA-256,
    fail the layer; exclude_from_solve matches the post-alias provider; a
    child profile may be listed before its parent in the same layer; a
    requirement updates every row that maps to its name and keeps an
    existing alias.
  • Package catalog: an exact version wins over an unversioned sibling,
    names and versions compare trimmed, a blank source is a missing-source
    error, replacing source resets an inherited format and drops
    inherited checksums, switching to easybuild-bump drops foreign
    checksums, and source_checksums must be SHA-256 digests.
  • LuaRocks: ~> is a series range, ~= a not-equal, build_dependencies
    are build edges, a git+ source is a git remote with its tag, hash
    counts only as a 64-hex SHA-256, external_dependencies are residuals,
    and the plan's easyblock is LuaRocks. Raku: ver<0.10+> is >=0.10
    and the ver, auth, api and from adverbs are not the name.
  • A git checkout source (a commit, or a remote with no download URL)
    emits a git_config dict.
  • A dependency that spells the module, ('OpenMPI', '5.0.3-GCC-13.3.0'),
    is an exact pin on that build, from a SYSTEM recipe too; it is not a hole.
  • Stack pins and exclusions apply to every toolchain-qualified key of a
    name; a locked pin on Perl constrains the GCCcore and SYSTEM builds.
  • The bump emits the plan's default profile; a layer's [package] version
    reaches the recipe while --version wins; a dependency stated in both
    lists is rewritten when either disagrees with the lock; a vanished
    dependency is removed wherever its tuple sits on the line; a sibling's
    patches and checksums are adopted with the emitted source digest
    kept and the plan's patch set rebuilt; local_host_arch, local_order
    and local_equations derive local_binary and parameterised
    configopts.
  • PyPI and PEP 518 requirements gated by an environment marker are opaque
    conditions, solver-excluded with a pypi-marker residual; build
    backends and overlay build tools are named only when the plan's own
    toolchain hierarchy provides them; a language bundle renders its
    patches, their checksums and configopts; the request's package index
    reaches the plan in prepare.
  • Closure: holes carry their versionsuffix into discovery, the companion
    key and the cycle path, so -MPI and -CUDA builds are two companions;
    an unversioned catalog wildcard defers to a unique versioned sibling; a
    PyPI or CRAN root the robot already provides closes without companions.
  • SBOM: only a 64-hex digest is a SHA-256 hash, the root hash is the first
    source that has one, overlay extensions are library components, and the
    GitHub archive URL is derived only from a github.com remote in any
    spelling.
  • CRAN sanity dirs sit under lib/R/library/<name>; a Spack
    type=("build", "link") dependency is a runtime edge.

Changed

  • A suffix or module spelling of a candidate answers only an exact
    requirement. Against a range it compared as a pre-release of its
    version, and <5 admitted a 5.0.0-GCCcore-13.3.0 build.
  • A GitHub archive whose repository differs from the package name spells
    the account and repository in source_urls; GITHUB_SOURCE would 404.
  • An uppercase declared patch digest verifies, a non-UTF-8 patch copies
    into the bundle, overlay claims key on the content digest, and a
    dummy-spelled source toolchain bumped onto system keeps its exact
    dependency pins.
  • A runtime extra that collapses onto a bundle a build-only extra already
    locked keeps the bundle off the build-only list.

Fixed

  • An MCP eb_package_bump call without a foreign array no longer fails
    with "argument foreign requires at least one path".

Install eb_stack 0.7.0

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/HaoZeke/eb-stack/releases/download/v0.7.0/eb_stack-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://github.com/HaoZeke/eb-stack/releases/download/v0.7.0/eb_stack-installer.ps1 | iex"

Download eb_stack 0.7.0

File Platform Checksum
eb_stack-aarch64-apple-darwin.tar.xz Apple Silicon macOS checksum
eb_stack-x86_64-apple-darwin.tar.xz Intel macOS checksum
eb_stack-x86_64-pc-windows-msvc.zip x64 Windows checksum
eb_stack-aarch64-unknown-linux-gnu.tar.xz ARM64 Linux checksum
eb_stack-x86_64-unknown-linux-gnu.tar.xz x64 Linux checksum

0.6.2 - 2026-11-08

Choose a tag to compare

@github-actions github-actions released this 08 Nov 13:45
v0.6.2
416a68f

Release Notes

Changed

  • rfc9162, rfc9162-tiles and rfc9162-log come from crates.io at
    exactly 0.8.1 instead of a git pin, so cargo package resolves them;
    0.8.1 reads a partial tile a writer has widened through the widest one,
    which a reader at a checkpoint behind the tail needs.

Fixed

  • The stack-gap-lint delivery (report, bundle, patches) lives under
    deliveries/stack-gap-lint/. At artifacts/ it sat where cargo-dist
    collects the release artifacts, and the 0.6.1 host step failed trying to
    upload artifacts/patches as a release asset.

Install eb_stack 0.6.2

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/HaoZeke/eb-stack/releases/download/v0.6.2/eb_stack-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://github.com/HaoZeke/eb-stack/releases/download/v0.6.2/eb_stack-installer.ps1 | iex"

Download eb_stack 0.6.2

File Platform Checksum
eb_stack-aarch64-apple-darwin.tar.xz Apple Silicon macOS checksum
eb_stack-x86_64-apple-darwin.tar.xz Intel macOS checksum
eb_stack-x86_64-pc-windows-msvc.zip x64 Windows checksum
eb_stack-aarch64-unknown-linux-gnu.tar.xz ARM64 Linux checksum
eb_stack-x86_64-unknown-linux-gnu.tar.xz x64 Linux checksum

0.3.0 - 2026-07-21

Choose a tag to compare

@github-actions github-actions released this 21 Jul 19:50
v0.3.0
ee836bb

Release Notes

First public release: package plan/bump/campaign CLI, Resolvo locks, CycloneDX
SBOMs, multi-platform installers (cargo-dist), and operator documentation.

Changed

  • The public eOn policy targets the core + with_rgpot product on a single
    foss-2026.1 / GCCcore-15.2.0 generation: no cross-generation PyTorch/xtb
    pins, no staged cargo-c preconfigopts, torch-family conda host deps
    excluded from the solve, and readcon-core plus rgpot closed as authored
    companion easyconfigs. fixtures/eon_core_rgpot freezes the upstream
    eOn 2.17.2 draft PR file set as the regression surface.

Added

  • skills/upstream-pr/SKILL.md: easybuild-easyconfigs PR conventions
    distilled from real merged and rejected PRs (single-generation closures,
    readable recipes, precedent citation, AI disclosure, test-report
    lifecycle).

  • MCP tools eb_recipe_lint and eb_stack_sbom, plus explicit optional
    schemas for eb_package_bump, eb_recipe_check, eb_recipe_format, and
    eb_stack_solve, so the MCP catalog matches the version-one CLI surface.

  • CI job for package catalog, package closure, closure write, and source-root
    discovery suites (previously only covered by local cargo test --all-targets).

  • Claim-ladder, command-surface, and pipeline diagrams (Graphviz source in the
    manuals; PNG/SVG under assets/illustrations/). CLI reference documents
    package catalog and source-root plan flags.

  • Package-neutral source-root discovery for package closure: ordered local
    EasyBuild, conda-forge, and Spack indexes close robot holes without a
    committed per-package catalog entry. Explicit catalogs remain optional
    overrides. EasyBuild bumps preserve toolchain family (for example GCCcore
    maps to the GCCcore member of the target hierarchy).

  • Public example examples/package-sources/local-roots.toml and CLI/MCP flags
    --package-sources, --easybuild-source, --conda-source, --spack-source.

  • Catalog provider kinds foreign (default) and easybuild-bump for
    package-source catalog entries, so recursive package closure can retarget an
    existing EasyBuild recipe through the annual-bump pipeline instead of
    substituting a foreign archive.

  • Public package-neutral catalog example at
    examples/package-catalog/mixed-providers.toml.

  • Canonical schema-versioned package plan shared by conda-forge, Spack, and
    EasyBuild inputs, with source provenance, structured conditions, variants,
    rules, build intent, product profiles, output requests, and residuals.

  • Planned CycloneDX SBOM generation from canonical package intent and solved
    EasyBuild stack locks, including primary source hashes, VCS identities, and
    hashed distribution references.

  • Per-profile materialization and Resolvo selection with preferred pins,
    locked pins, candidate exclusions, and recorded fallback outcomes.

  • One conventional EasyBuild recipe and profile lock per installable product
    profile; default profiles remain unsuffixed.

  • Positional source-checksum overrides at the CLI and MCP emission boundary,
    with complete source coverage required before a recipe is emitted.

  • Canonical new-package and bump bundles containing package.plan.json,
    package.sbom.cdx.json, profile locks, and EasyBuild recipes.

  • Layered public TOML build targets covering local/SSH transport,
    direct/Slurm execution, host/Podman/Docker runtime, and EasyBuild workload.

  • Persisted build campaigns with exact routed commands, independent claim
    ladder, typed findings, ownership, resolution evidence, and retry
    supersession.

  • Profile binary-verification commands with package/module/profile
    placeholders.

  • Version-one CLI and MCP surfaces for package planning, recipe checks, stack
    solving, targets, campaigns, and finding coordination.

  • Public new-package and annual-bump skills implementing the Hermes/OMP
    build-evaluation loop.

Changed

  • Existing-recipe bumps use the same SBOM, manifest, Resolvo lock, EasyBuild
    emission, target routing, and campaign model as new packages.
  • Existing robot artifacts keep independent build-only dependency contexts
    during package-profile solving, matching EasyBuild's installed artifact
    model.
  • Recipe style lint/format is namespaced under recipe and remains purely
    mechanical.
  • Documentation, examples, CI, and acceptance fixtures use only the
    version-one command and MCP names.
  • CI enforces the Rust 1.88 minimum, formatting, clippy with warnings denied,
    and public metadata contracts.
  • Rust-backed fixture recipes reset Cargo compiler wrappers without exposing
    host configuration inherited through mounted build paths.
  • Campaign state uses an OS-backed exclusive guard with process-identity
    metadata, so interrupted controllers do not leave permanent stale locks.

Removed

  • The unreleased scaffold ingest, companion placeholder, intermediate plan,
    standalone bump, and auto-emitter APIs.
  • Compatibility shims and legacy CLI/MCP command names.
  • Generated placeholder recipes with dummy sources or checksums.

Install eb_stack 0.3.0

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/HaoZeke/eb-stack/releases/download/v0.3.0/eb_stack-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://github.com/HaoZeke/eb-stack/releases/download/v0.3.0/eb_stack-installer.ps1 | iex"

Download eb_stack 0.3.0

File Platform Checksum
eb_stack-aarch64-apple-darwin.tar.xz Apple Silicon macOS checksum
eb_stack-x86_64-apple-darwin.tar.xz Intel macOS checksum
eb_stack-x86_64-pc-windows-msvc.zip x64 Windows checksum
eb_stack-aarch64-unknown-linux-gnu.tar.xz ARM64 Linux checksum
eb_stack-x86_64-unknown-linux-gnu.tar.xz x64 Linux checksum