melosso/portway v1.5.4

on GitHub

Fixes in v1.5.4:

• fix(middleware): Optimized RateLimitingMiddleware with static JSON options and improved timer cleanup logic, and disabled rate limiting for authenticated UI visitors.
• fix(stability): Ensured safe shutdown upon distributed lock for endpoints.
• fix(tests): Resolved authentication and telemetry test failures by rewriting tests after a parallel race condition in the MCP extension.
• fix(tests): Updated mocks and assertions to match the current architecture.
• fix(ui): Adjusted the drawer position to ensure it sits flush below the promobar.
• fix(ui): Clarified and enhanced UI animations and interactions for smoother user experience.
• fix(ui): Fixed styling issues in the frontend for better visual consistency.
• fix(ui): Added a closable modal for MCP UI dialogs to improve user control.
• fix(ui): Updated demo endpoints for consistency.
• fix(parser): Escaped characters in YAML for parser compatibility.
• fix(deployment): Copied start.sh after OCI runtime errors to ensure proper startup.
• fix(deprecation): Removed the deprecated tokengenerator tool.
• fix(auth): Registered ITokenVerificationCache as a singleton within AuthServiceExtensions.

New features in v1.5.x:

• Support for Model Context Protocol (MCP) – Expose your endpoints natively or just chat without leaving Portway
• Standardized Response Types – Introduced PortwayResponse.cs and PortwayResults for consistent API responses.
• OpenTelemetry Instrumentation – Added telemetry for monitoring performance and errors.
• Improved Concurrency – Enhanced thread safety and resource management.
• Refactored DI – Simplified service registration with extension methods.
• Schema Standardization – Updated schemas for webhooks and file endpoints.

Migration guide

As 1.5.0 has introduced breaking changes, please follow the following steps for a safe upgrade path:

1. Update Docker configurations. If you are running Portway in a container, please check the updated documentation regarding the ASP.NET port mappings, as these have changed.
2. Configure Web UI access. If you plan to access the admin console externally, ensure you explicitly enable external traffic routing in your (appsettings.json) settings.
3. Verify your File & Webhook endpoints. The structure of these have changed slightly,
   Check our documentation for guidance. If you encounter issues, open a new Issue.

Check our documentation for guidance. If you encounter issues, open a new Issue.

Full Changelog: v1.5.3...v1.5.4