Changelog and Versioning

Navigation: [Home]] ](/AGI-Corporation/frontier-os-app-builder/wiki/[Developer-Guide) | [Pipeline Registry]]

Versioning Policy

Agent.bay follows Semantic Versioning (SemVer) 2.0.0 for all pipelines and platform APIs.

• MAJOR: Incompatible changes (e.g., changing required manifest fields).
• MINOR: Additive changes (e.g., new optional capabilities).
• PATCH: Backward-compatible bug fixes.

Platform Changelog

v1.2.0 (Planned)

• Feature: Multi-Hop agent verification via NANDA Integration.
• Feature: Native support for DeSci and Regulated Industries.
• Optimization: Sandbox boot time reduced by 30% using Agent Runtime and Sandbox snapshots.

v1.1.0 (Current)

• Feature: Integrated Bitrefill Funding and x402 Payments for prepaid agent spending.
• Feature: Enhanced Security and Trust Model with Proof of Intent.
• Update: CLI now supports frontier logs for real-time debugging.

v1.0.0 (Release)

• Core: Initial release of the Pipeline Registry and Task Dispatch and Routing Logs.
• Core: Support for Python and Node.js sandboxed runtimes.
• Governance: Launch of the DAO Governance and Staking bridge.

Pipeline Versioning

Developers are encouraged to maintain immutable versions of their logic. When a pipeline is updated in the registry:

1. The new logic is assigned a unique content hash.
2. The version number is incremented in the manifest.
3. Existing users can choose to "Pin" a specific version to ensure deterministic behavior.

---

Related Pages

• Roadmap – Future features and releases
• Pipeline Registry – How versions are stored
• Developer Guide – Best practices for versioning your logic
• API Reference – API versioning headers