Skip to content

v0.9.0-rc.3

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 11 Nov 16:34
· 225 commits to main since this release

Changes

Added

  • Anyone can read what the hub, hub.aggrega.ai, publishes without a login; publishing to it still needs credentials.
  • Every import walkthrough ends by running what the build wrote and showing it answer a request.
  • A Windows installer installs Aggrega without administrator rights, through a wizard offering the install folder, an Add to PATH choice and the next steps.
  • The daemon's plugin-add answer carries withdrawn: true when the version you named has been retracted, as the command line says.

Changed

  • Documents, schemas, plugins and published artifacts use aggrega.ai/v1beta1, which changes only additively; a document or plugin still on v1alpha1 is refused.
  • Releases promise compatibility from 0.9.0 for schemas, commands, flags, assistant tools, error codes and plugin kits, as the new Compatibility page states.
  • The plugin kits and ABI codecs follow semantic versioning from 0.9.0, and a change breaking their API ships only in a new minor version.
  • Catalog components running your own image deliver each own value under a default variable name, which a component-level inject: block can rename; Recipes read .context.self_inject.
  • An inject block naming a mechanism all is refused with its reason, and a schema not branch's own description is printed as its refusal.
  • Importing a folder no importer recognises suggests importing one of its files, or naming a format whose importer reads folders.
  • A build whose catalog holds no parser for a format reads it through the compiler's built-in parser, as an import does.
  • Commands show progress while they wait, print the workspace warning only where it applies, and plugin add cli <name>[:<version>] works outside a workspace.
  • Commands wait as long as a busy registry asks, send it fewer requests at once, and stop by name after five minutes of slow-down answers.
  • LangGraph Recipes hand the graph its recursion limit, its checkpointer store's password, and the store's user and database where it publishes them.
  • The Claude Desktop package runs the aggrega on your PATH and asks you to set an empty Workspace folder.

Fixed

  • Kubernetes accepts builds whose Aggregate name or environment holds /; the label is rewritten and the exact value kept as an annotation.
  • An unmapped Feature's refusal lists the FeatureRecipes implementing its type for the component's target, or those for other targets when none fits.
  • With no catalog directory, the refusal for an unmapped component or Feature says it searched only the lockfile's pins.
  • Lockfiles record each entity's kind, keeping same-named entities of different kinds apart, and pull --detail names each kind correctly.
  • aggrega pull fetches and pins the base a Component or Feature extends, so wrappers build and validate without mapping their base.
  • A governance plugin at a label or annotation transform role builds from the hub with no catalog directory.
  • A verdict policy naming another release of a built-in governance plugin runs the compiler's own engine.
  • A Feature attachment's inject entry written with value: is refused; write the literal in the component's own block.
  • An attachment inject entry whose from: names a key its FeatureRecipe does not publish is refused, unless the FeatureRecipe reads .inject itself.
  • A refusal whose own sentence quotes nothing sensitive is printed, and the duplicate-delivery-key refusal says how to give each attachment its own key.
  • Helm compute Recipes refuse a credential Feature they cannot deliver, by name, and Helm secret realizations refuse a Compose-style ${…} origin.
  • Import drafts describe LangGraph images and =Env. references correctly, name Agent Framework MCP servers in comments, and leave non-Gemini ADK models unwired.
  • The Google ADK import's draft header says ADK also serves some providers' models, such as claude-… and gpt-… names, through classes of its own.
  • Dify built for Kubernetes starts every service, stays up and answers requests; its import step prints Dify's refusal and stops retrying.
  • The Dify plugin runtime and LangGraph Compose Recipes run no shell syntax and accept quotes in a connected store's address.
  • On Docker Compose, a LangGraph graph starts once its store accepts connections.
  • Langflow on Docker Compose can write to its data volume, and Ollama defaults to 0.15.6, serving the Responses API.

Install

These commands install this release, 0.9.0-rc.3.

Linux and macOS:

curl -fsSL https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.9.0-rc.3/install.sh | AGGREGA_VERSION=0.9.0-rc.3 sh

Windows (PowerShell):

$env:AGGREGA_VERSION = '0.9.0-rc.3'; irm https://github.com/aggrega-ai/aggrega-cli/releases/download/v0.9.0-rc.3/install.ps1 | iex

Both install the default aggrega for the current user and check it against SHA256SUMS.

Windows installer: run aggrega-0.9.0-rc.3-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.9.0-rc.3-<os>-<arch> The default build, with the core plugins embedded
aggrega-debug-0.9.0-rc.3-<os>-<arch> The same build with debug information, for a debugger or a profiler
aggrega-light-0.9.0-rc.3-<os>-<arch> No embedded plugins; resolves plugins through the cascade
aggrega-0.9.0-rc.3-windows-amd64-setup.exe Windows installer
aggrega-0.9.0-rc.3.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.