Skip to content

Releases

v1.3.0

Choose a tag to compare

@bintangtimurlangit bintangtimurlangit released this 20 Jun 22:05

Build-plate fit and support detection for every estimate.

Added

  • Build-plate fit: /slice responses now include model_dimensions_mm, build_volume_mm, and fits_build_volume. Default build volume is 256×256×256 (BUILD_VOLUME_X/Y/Z), overridable per request (build_volume_x/y/z). Over-sized models are flagged, not rejected — they slice on an enlarged bed and still return estimates instead of a 500.
  • requires_supports flag, detected from a support-enabled slice (check_supports, on by default; set false to skip).
  • Postman collection at docs/superslice.postman_collection.json.

Changed / Removed

  • README: Mermaid "How it works" + "Why PrusaSlicer 2.8.1?" note.
  • Removed docs/SLICER.md and docs/ROADMAP.md (folded into the README); trimmed GHCR account-setup from docs/DEPLOYMENT.md.

Full Changelog: v1.2.0...v1.3.0

v1.2.0

Choose a tag to compare

@bintangtimurlangit bintangtimurlangit released this 20 Jun 21:26

Async jobs, opt-in protection, slicing history, and structured errors — plus a package reorganization. All new protection/history features are opt-in and disabled by default.

Added

  • Async job mode: POST /jobs → 202 + job id; poll GET /jobs/{job_id}.
  • Opt-in API-key auth (API_KEYS), rate limiting (RATE_LIMIT_PER_MINUTE), and a concurrency cap (MAX_CONCURRENT_SLICES).
  • Opt-in slicing history (HISTORY_ENABLED, SQLite): GET /history, GET /history/{id} — parameters + results, never model files.
  • Disk-space guard (MIN_FREE_DISK_MB) and a startup sweep of orphaned work files.
  • GET /healthz and GET /version; OpenAPI examples.

Changed

  • Structured error responses: stable error.code alongside detail.
  • Reorganised app/ into api/, core/, and services/ layers.
  • Healthcheck now targets /healthz; fixed the reported API version.

Full Changelog: v1.1.0...v1.2.0

v1.1.0

Choose a tag to compare

@bintangtimurlangit bintangtimurlangit released this 20 Jun 21:02

Self-owned PrusaSlicer image, API hardening, tests, docs, and release tooling.

Changed

  • Self-owned Docker image — replaced the third-party mikeah/prusaslicer-novnc base with a multi-stage build that downloads, SHA-256-verifies, and extracts the official PrusaSlicer 2.8.1 AppImage (the last AppImage release; 2.9+ is Flatpak-only). Runs as a non-root user.
  • docker-compose.yml: dropped the obsolete version key, added a healthcheck.

Added

  • pytest unit + API suite (tests/) and requirements-dev.txt.
  • In-depth docs under docs/ (architecture, slicer rationale, accuracy, troubleshooting, roadmap).
  • CI test workflow; release process in RELEASING.md; issue/PR templates.

Fixed

  • Enforce MAX_FILE_SIZE and reject empty uploads (correct 4xx instead of 500).
  • Harden time-string parsing (missing units / days).
  • Run the blocking slicer subprocess off the event loop.
  • Reconcile models.py bounds with validation; create work dirs with parents=True.

Full Changelog: v1.0.0...v1.1.0

v1.0.0

Choose a tag to compare

@bintangtimurlangit bintangtimurlangit released this 08 Feb 14:46

Initial Release

SuperSlice v1.0.0 - A REST API service for 3D print estimation using PrusaSlicer.

Features

  • RESTful API for 3D model slicing with PrusaSlicer
  • Support for STL and 3MF file formats
  • Configurable slicing parameters (layer height, infill density, wall count)
  • Predefined filament types with accurate density calculations (PLA, PETG, ABS, TPU, NYLON, ASA)
  • Custom filament density override support
  • Docker-based deployment with health checks
  • Automated CI/CD pipeline with GitHub Actions
  • Comprehensive API documentation (Swagger UI and ReDoc)

Docker Images

Pull the image from GitHub Container Registry:

docker pull ghcr.io/bintangtimurlangit/superslice:1.0.0

Or use the latest tag:

docker pull ghcr.io/bintangtimurlangit/superslice:latest

Quick Start

docker run -d -p 8000:8000 ghcr.io/bintangtimurlangit/superslice:1.0.0

Documentation

What's Changed

Initial production-ready release with modular codebase, comprehensive documentation, and automated Docker image publishing.