Table of Contents

Changelog

Welcome to the Jiro.Shared changelog. This section contains detailed information about all changes, updates, and releases for each version of the shared types and models library.

Available Versions

  • v1.3.2 "Seisō" - Clean logging optimization by removing verbose request/response body logging
  • v1.3.1 "Seigō" - Precision & reliability fixes with SignalR serialization improvements and enhanced logging
  • v1.3.0 "Ōtō" - Response acknowledgment with ActionResult returns and channel-based streaming
  • v1.2.2 "Tsuiseki" - Stream request tracking with request ID support and improved hub method organization
  • v1.2.1 "Bunri" - Streaming architecture refinement with two-phase streaming pattern
  • v1.2.0 "Nagare" - Streaming support for logs and session messages with IAsyncEnumerable
  • v1.1.6 "Shinpo" - Progress enhancement with improved connection handling, thread safety, and enhanced logging for JiroClientBase
  • v1.1.5 "Kiban" - Foundation strengthening with JiroClientBase abstract class for simplified client implementations
  • v1.1.4 "Chōwa" - Interface harmony with clearer WebSocket interface naming conventions
  • v1.1.3 "Kizen" - Foundation refinement with enhanced session request models and improved API consistency
  • v1.1.2 "Shinpo" - Progress and advancement with documentation improvements and bug fixes
  • v1.1.1 "Byakko" - Response handler methods with [HubMethodName] attributes for all client-to-server responses
  • v1.1.0 "Kaizen" - Enhancement release with system monitoring, memory cache utilities, and database extensions
  • v1.0.1 - Patch release fixing NuGet package display issues
  • v1.0.0 "Hajimari" - Initial release with WebSocket endpoints, gRPC definitions, and shared models

Resources

About This Section

Each version has its own dedicated changelog file with comprehensive details about:

  • ✨ Features Added - New functionality and capabilities
  • 🔄 Changes - Modifications to existing features
  • 🐛 Bug Fixes - Issues resolved in the release
  • 🛠️ Technical Details - Architecture and implementation changes
  • 📊 Metrics - Release statistics and performance data

Versioning

Jiro.Shared follows semantic versioning (SemVer) with meaningful code names:

  • Code Names: Each major release includes a Japanese-inspired code name that reflects the theme of the release
  • Semantic Versioning: MAJOR.MINOR.PATCH format following SemVer principles
  • Release Branches: Releases are tagged from the main branch

This project follows Semantic Versioning (SemVer) for version numbering.

Edit this page