Repository navigation
v0.8.11
Changes
Added
- The documentation, catalog and home sites are now published in Italian, German, French, Spanish, Brazilian Portuguese and European Portuguese.
- The home page explains how Aggrega works with translated diagrams and icons, and the documentation adds diagrams of Features, roles and AI gateways.
- A plugin diagnostic's location can name the component it concerns in a new
instancefield, kept apart fromuri, which names a document. - A new Import section teaches
aggrega import, with a walkthrough for every format it reads that takes a project to a build. - Getting started and two examples now show diagrams of how Aggrega works, of one application on many platforms, and of build-time policies.
- The import walkthroughs build as written, say where to clone the standard-library catalog, and run CrewAI and LangGraph on Docker Compose.
Changed
- Compose sidecar and init services are now named
<component>--<container>, so containers of different components no longer share a name; existing ones are recreated. - Catalog credential slot descriptions now name the development value a Recipe uses when the slot is unattached, a value every such Release shares.
- A diagnostic about one component now names it as
(instance <name>)after the file, orinstance <name>alone, never where a file belongs.
Fixed
- Imported drafts build without hand repair: each connection gets its own alias, Langflow's OpenAI model is wired, and drafted Releases place every model and datastore.
aggrega importuses its built-in importer when the catalog holds importer entries without their module, and a registry refusal says to re-run the import.- Compose builds of CrewAI, LangGraph and PostgreSQL accept a credential that only the Release attaches.
aggrega validate <entity>and the assistant'scatalog://resource now name the broken catalog file skipped at load instead of only reporting the entity not found.- The RDS Recipes now document
subnet_group,parameter_groupandvpc_security_groupsas override keys shared across AWS Recipes, not Terraform argument names. - A Recipe with
source: ""is now refused when loaded, sopull,buildandvalidateall reportE0251, advising to omit or fill the field. aggrega validatenow refuses a Component or Feature whose socket or slot selector cannot be parsed, even when nothing wires that socket or slot.aggrega lint <plugin.yaml>now reads the.wasmbeside the entity, where guest builds now write it, and notes what the entity leaves undeclared.- An empty
inject: {}on an attachment filling a slot that permits no delivery now builds inside imported modules and subsystem-wide attachments too. - A boundary's
subDirectory: "{{ .component_id }}"now names a boundary-scope Feature attachment's folder after itsaggrega.ai/component-idlabel, not an internal marker. aggrega inspect,aggrega validate --releaseand the assistant's matching tools now refuse an out-of-date lockfile with the build'sE0130halt.- A template reading
.inject_rawnow sees a component's custom inject mechanisms, such asssm_param, besideenv,fileandarg. - A FeatureRecipe's
valuesMappingnow reads its ownsource:at.source, never the source of the component it is attached to. aggrega registry updateshows its progress while it walks a registry, asbuildandpulldo.- In the editor, a Manifest mapping fault now appears on the Manifest, at the faulty mapping entry, instead of on the Aggregate.
- The Strimzi and RabbitMQ operators are now workers: broker sockets refuse them at
validate, while Prometheus'sscrape_target,core/prometheus-exporterandcore/caller-allowlistaccept workers. - With nothing attached to its backend credential, Langfuse now presents the catalog's development database password and can sign in to a catalog PostgreSQL.
- Helm builds now refuse a component name giving a CronJob over 52 characters or a Service over 63, and shorten a Feature attachment's name instead.
Install
These commands install this release, 0.8.11.
Linux and macOS:
curl -fsSL https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.8.11/install.sh | AGGREGA_VERSION=0.8.11 shWindows (PowerShell):
$env:AGGREGA_VERSION = '0.8.11'; irm https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.8.11/install.ps1 | iexBoth install the default aggrega for the current user and check it against SHA256SUMS.
Windows installer: run aggrega-0.8.11-windows-amd64-setup.exe. No administrator rights; installs into %LOCALAPPDATA%\Programs\aggrega and adds it to your PATH. /S installs silently; uninstall.exe /S in that folder removes it.
Homebrew and Scoop install the newest release: brew install aggrega-ai/tap/aggrega, or scoop bucket add aggrega https://github.com/aggrega-ai/scoop-bucket then scoop install aggrega.
Files
Binaries for linux/amd64, linux/arm64, darwin/arm64, darwin/amd64 and windows/amd64 (.exe):
| File | What it is |
|---|---|
aggrega-0.8.11-<os>-<arch> |
The default build, with the core plugins embedded |
aggrega-debug-0.8.11-<os>-<arch> |
The same build with debug information, for a debugger or a profiler |
aggrega-light-0.8.11-<os>-<arch> |
No embedded plugins; resolves plugins through the cascade |
aggrega-0.8.11-windows-amd64-setup.exe |
Windows installer |
aggrega-0.8.11.mcpb |
Claude Desktop extension: runs an installed aggrega as a local MCP server; one file for every OS |
install.sh, install.ps1 |
Install scripts |
SHA256SUMS |
SHA-256 of every other file; check with sha256sum -c SHA256SUMS |
Signing: Windows files carry a timestamped Authenticode signature from Cognitio S.r.l.; macOS files are signed with the Developer ID of COGNITIO SRL and notarized by Apple.