You are reading the documentation for v2.1.1, which is not the current version. It describes that release and is kept for reference. It is not updated.Go to v3.1.0 β†’

Release Notes

Release notes for the v2.x line, newest release first. Every release in this line is on this page.

Coming from v1? v2.0.0 breaks integrations - its section below has the migration guide. Nothing after it does.

πŸ›‘οΈ The Service Module is exempt from these notes. From v2.0.0 it is developed for the hosted service, so a breaking change to it is not documented here and does not force a major version increment. If you self-host with the Service Module enabled, read every release before upgrading - a minor or patch release can break it. Everything else on this page follows the usual rules. See the Service Module page.


v2.1.1

Released 12 January 2026 - release on GitHub

πŸ”Ž Overview

βš™οΈ Core Changes


v2.1.0

Released 3 December 2025 - release on GitHub

πŸ”Ž Overview

βš™οΈ Core Changes

🎨 UI Module


v2.0.1

Released 2 October 2025 - release on GitHub

πŸ”Ž Overview


v2.0.0

Released 2 October 2025 - release on GitHub

Binacle.Net v2.0.0 is a major update from v1.3.0.

v2.0.0 introduces breaking changes and new features. Existing integrations must be reviewed and updated.

πŸ”Ž Overview

βš™οΈ Core Changes

πŸ§ͺ Diagnostics Module

πŸ”Œ Service Module

The Service Module was entirely rewritten and its business logic has been fundamentally changed.

For additional details, see the Service Module documentation.

🎨 UI Module

πŸ“ˆ Algorithms

πŸ—οΈ Internal Work

πŸ“š Versioned Docs

πŸ› οΈ Migration Guide

To upgrade to v2.0.0, follow these steps:

  1. Remove all V1 usage
    • Any calls to V1 endpoints must be removed or migrated.
  2. Review log configuration
    • All logs under /app/data/logs now use the yyyyMMdd.ndjson format instead of log-yyyyMMdd.txt.
  3. Switch to V2 or V3 endpoints
    • Update integrations to use stable V2 or V3 endpoints.
    • Verify that algorithms behave correctly with the updated logic.
  4. Update Packing Logs usage
    • Replace any use of legacy-fitting and legacy-packing in /app/data/pack-logs with the new packing and fitting paths.
  5. Service Module users
    • All integrations with the old Service Module will no longer work.
    • No public documentation is available. Please contact directly if needed.
    • For self-hosted setups, you will need to rely on the source code, as documentation will not be provided.
  6. Adopt new documentation
    • If you previously relied on the legacy JSON documentation, migrate to OpenAPI 3.0.
    • Use Swagger UI or Scalar UI for interactive references.