Skip to content

Releases: bivektor/reportshell

v1.3.1

04 May 21:52

Choose a tag to compare

Summary

This release fixes a critical connection leak in control option loading flows. The leak could occur when JDBC connection timeouts or similar connection failures interrupted option loading.

Users are strongly encouraged to upgrade.


Note: This repository contains only samples. Releases here exist solely to publish release notes. The attached source archives are intentionally empty.

API Stability for 1.x: The 1.x release line is functionally stable and production-suitable, but the public Java/Kotlin API surface is still considered unstable until 2.0. Breaking changes in public Java/Kotlin APIs may occur in 1.x minor releases while we finalize naming, extension points, and API shape based on early-adopter feedback. Runtime behavior, REST endpoints, and report semantics are intended to remain compatible throughout the 1.x line.

v1.3.0

30 Apr 13:15

Choose a tag to compare

Superseded: This version has been superseded by 1.3.1, which fixes a critical connection leak in control option loading flows. Users should upgrade to 1.3.1.

Summary

This is the first functionally stable release of ReportShell. It marks the point where the core viewer flow, Spring Boot integration, REST API behavior, and report execution semantics are suitable for production evaluation and early production use.

Earlier pre-stable release entries were removed as part of resetting the public package history. No production-compatible package line should be assumed before 1.3.0.

Note: This repository contains only samples. Releases here exist solely to publish release notes. The attached source archives are intentionally empty.

API Stability for 1.x: The 1.x release line is functionally stable and production-suitable, but the public Java/Kotlin API surface is still considered unstable until 2.0. Breaking changes in public Java/Kotlin APIs may occur in 1.x minor releases while we finalize naming, extension points, and API shape based on early-adopter feedback. Runtime behavior, REST endpoints, and report semantics are intended to remain compatible throughout the 1.x line.